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.

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

Add malleable fields to transaction subscription #1724

Closed
Dentosal opened this issue Mar 4, 2024 · 0 comments · Fixed by #2061
Closed

Add malleable fields to transaction subscription #1724

Dentosal opened this issue Mar 4, 2024 · 0 comments · Fixed by #2061
Assignees
Labels
graphql-api Affects API of the GraphQL

Comments

@Dentosal
Copy link
Member

Dentosal commented Mar 4, 2024

From @nedsalk

Subscriptions currently return receipts, but they're not the only transaction-related data that's set on the node during execution; there are others like some transaction outputs, the receipts root, etc. Would it be possible for the subscriptions to return all the data that changes on a transaction after it's executed? Currently as it stands, the TS SDK creates a transaction summary that the frontend team uses in various use cases. Without e.g. the outputs on the subscription, we have to do another call to fetch them for the summary to be complete. This need for an additional fetch diminishes the benefits of the subscription even if we read the receipts from it.

Related to FuelLabs/fuels-ts#1644

@Dentosal Dentosal added the graphql-api Affects API of the GraphQL label Mar 4, 2024
xgreenx added a commit that referenced this issue Aug 9, 2024
Closes #1724

### Before requesting review
- [x] I have reviewed the code myself
@xgreenx xgreenx self-assigned this Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
graphql-api Affects API of the GraphQL
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants