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

Simplify GraphQL interfaces #1652

Closed
Voxelot opened this issue Feb 8, 2024 · 0 comments · Fixed by #1675
Closed

Simplify GraphQL interfaces #1652

Voxelot opened this issue Feb 8, 2024 · 0 comments · Fixed by #1675
Assignees
@Voxelot

Comments

@Voxelot
Copy link
Member

Voxelot commented Feb 8, 2024

We should simplify some of the graphql interfaces to avoid issues like this from happening: FuelLabs/fuels-ts#1706

Specifically, users shouldn't need to be able to query every field of a contract within a receipt, and this could just be simplified to returning only the ContractId.
@Voxelot Voxelot mentioned this issue Feb 17, 2024
Merged
@Voxelot Voxelot self-assigned this Feb 17, 2024
xgreenx pushed a commit that referenced this issue Feb 18, 2024
@Voxelot
Remove nested contract resolvers in GQL schema (#1675)
a838222 
closes: #1652

Having the ability to fetch all data related to a contract is overkill
and costly in most cases, and usually done by accident. This api change
simplifies the GQL schema to simply return a contractId instead of a
contract resolver for tx inputs, receipts, and more.

Note that the full contract details (such as the contract bytecode) can
still be fetched directly via the contract query endpoint.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Voxelot Voxelot

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove nested contract resolvers in GQL schema FuelLabs/fuel-core
1 participant
@Voxelot