feature: Allow options to be passed to simulate calls on the transaction composer, and properly type the return values. #92
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
|
Fixes #93 |
… composer, and properly type the return values
robdmoore
force-pushed
the
feature/allow-options-in-simulate
branch
from
b50814d
to
88e3571
Compare
robdmoore
approved these changes
Jan 26, 2024
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.
…
Proposed Changes
.simluate()on a transaction composer, you can now pass in options that are forwarded to the underlyingatc.simulate()call. For exampleclient.someCall().simulate({ allowEmptySignatures: true })returnsproperty (similar to the.execute()response) containing mapped return values.