Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Optimize transaction's graphql queries #3289

Open
1 of 5 tasks
arboleya opened this issue Oct 9, 2024 · 0 comments
Open
1 of 5 tasks

Optimize transaction's graphql queries #3289

arboleya opened this issue Oct 9, 2024 · 0 comments
Assignees
@Torres-ssf
Labels
chore Issue is a chore

Comments

@arboleya
Copy link
Member

arboleya commented Oct 9, 2024 •
edited by Torres-ssf
Loading

During some load tests, we realized a couple of issues (#3279, #3277) that we're fixing and optimizing.

In keeping with this theme, we should continue the effort and review our predefined GQL queries and fragments.

Every field removal is a breaking change and can break things for apps, so we need to be extra careful here.

Taking from the providers/operations.graphql:

  • getTransaction
  • getTransactionWithReceipts
  • getTransactions
  • getTransactionsByOwner
  • getRelayedTransactionStatus
@arboleya arboleya added the chore Issue is a chore label Oct 9, 2024
@Torres-ssf Torres-ssf self-assigned this Oct 9, 2024
@Torres-ssf Torres-ssf mentioned this issue Oct 15, 2024
Draft
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Torres-ssf Torres-ssf

Labels
chore Issue is a chore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arboleya @Torres-ssf