-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: optimize getTransactions
query
#3336
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CodSpeed Performance ReportMerging #3336 will not alter performanceComparing Summary
|
Coverage Report:
Changed Files:
|
@@ -0,0 +1,5 @@ | |||
--- | |||
"@fuel-ts/account": patch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"@fuel-ts/account": minor
Isn't this a breaking change given we changing the response of getTransactions
to return two less fields? i.e. the id
and transactionStatusFragment
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But @maschad The Provider.getTransactions has exactly the same response, no property was removed from it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with you but if someone called provider.operations.getTransactions()
the response would change and thus it's breaking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM apart from the changeset 👍🏻
Release notes
In this release, we:
Provider.getTransactions
Summary
This PR updates the getTransactions query to return only the
rawPayload
propertyThe Provider.getTransactions method, which uses this query, only requires the
rawPayload
property. Therefore, the broadertransactionFragment
, which includes unnecessary data, is no longer used.Since the
Provider.getTransactions
method did not use the additional fetched data included attransactionFragment
, this change does not introduce any breaking changes.Checklist