fix: use fuels pr-2479 to ensure correct operations are shown #1419
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
maschad
requested review from
luizstacio,
pedronauck,
LuizAsFight,
helciofranco,
arthurgeron and
rodrigobranas
as code owners
|
I think it may be best to cherry-pick the commit once this is merged into master onto a patch release based off |
5 tasks
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.
Closes Approve Screen: Randomly not showing operations #1415
Related to fix: return correct operations from coin and message inputs fuels-ts#2782
Summary
When approving a transaction from a dApp, for instance connectors.fuel.network , the operations were not being displayed properly, particularly when there was only an
InputMessagein the connecting wallet. This is due to a bug in the fuel-ts SDK where the associatedInputMessages andInputCoinswere not being returned. This PR seeks to upgrade to that fix, which will eventually be released in fuels-tsv0.92.2Notes
In the screenshots below is the related fix