Add support for calling the two-arg variant of runTransaction #38
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
When given a first argument closure that returns a non-optional type, the compiler would give up trying to match against the two-arg variant and instead complain about the first argument missing a `with:` label and not being a `TransactionOption` type. A fix for this is to provide optional and non-optional variants of the two arg override.
brianmichel
approved these changes
Feb 26, 2024
|
Thank you! |
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.
When given a first argument closure that returns a non-optional type, the compiler would give up trying to match against the two-arg variant and instead complain about the first argument missing a
with:label and not being aTransactionOptiontype.A fix for this is to provide optional and non-optional variants of the two arg override.