Block identifier #596
Merged
Block identifier #596
Conversation
This file contains 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
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.
What I did
Expose
block_identifierwhen making contract callsCloses #586
How I did it
Added the
block_identifierkwarg where it made sense. This is the same syntax thatweb3.pyuses.The only non-trivial thing I encountered was the case where calls are always handled as transactions (when evaluating coverage, for example). In this case, if the kwarg is provided I've opted to forgo running it as a transaction - since we can't very effectively perform a tx against historic state.
How to verify it
Run tests. I added some new test cases.