-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
CodSpeed Performance ReportMerging #3336 will improve performances by ×2.4Comparing Summary
Benchmarks breakdown
|
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 👍🏻
getTransactions
querygetTransactions
query
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.
Could we add a migration suggestion to the breaking changes? Maybe just a suggestion to user Provider.getTransactions
?
Coverage Report:
Changed Files:
|
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.Breaking Changes
The response format for
Provider.getTransactions
remains the same. However, the response format for the queryProvider.operations.getTransactions
has been modified.Checklist