Support mapping events for transactions with multiple operations#133
Merged
Support mapping events for transactions with multiple operations#133
Conversation
Contributor
Coverage reportCaution Test run failed
Test suite run failedFailed tests: 1/72. Failed suites: 1/8.Report generated by 🧪jest coverage report action from afefbd3 |
9 tasks
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
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.
Description
Up until now, we had not come across a case where a transaction had multiple operations and events emitted. There was an assertion so we would catch this case. Now that we have found a transaction we can correctly handle it.
We now also map the events to the operations correctly using the operationIndex that is not exposed via typescript types but exists on the object
Fixes #131
Type of change
Please delete options that are not relevant.
Checklist