Update documentation for transaction hash fetching #11546
Merged
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ritzdorf
requested review from
DaniPopes,
klkvr,
mattsse,
grandizzy,
yash-atreya,
zerosnacks and
onbjerg
as code owners
zerosnacks
reviewed
Sep 4, 2025
yash-atreya
approved these changes
Sep 4, 2025
DaniPopes
approved these changes
Sep 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed the documentation to clarify which state is using in
--fork-transaction-hash.Here is the source:
https://github.com/foundry-rs/foundry/blob/961241c02fb06143608d5b985a1bae793ac8f172/crates/anvil/src/config.rs#L1442C26-L1442C35
Motivation
It really was not clear to me when reading the option whether I would get the state BEFORE or AFTER that transaction has been executed. Also ChatGPT claimed BEFORE.
Solution
I, hopefully, clarified the docs.