We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When generating a client using fragments and lots of similar queries that use the same fragment it leads to lots of the same structs being generated.
Ideally there would be a seperate Fragments struct that contains the defined fragments.
I.e the following queries would both share the same response structs as they use the same fragment:
fragment LoadInfo on Load { loadId jobContainerId name loadPlanStatus journey { journeyId } } query loadById($load: Int!) { loadByID(loadId: $load) { ...LoadInfo } } query loadBySupplier($supplier: String!, $after: LocalDateTime!) { loadsBySupplierId(supplierCode: $supplier, after: $after) { ...LoadInfo } }
Not sure how feasible that is, but I think something similar is done for input types and enums?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When generating a client using fragments and lots of similar queries that use the same fragment it leads to lots of the same structs being generated.
Ideally there would be a seperate Fragments struct that contains the defined fragments.
I.e the following queries would both share the same response structs as they use the same fragment:
Not sure how feasible that is, but I think something similar is done for input types and enums?
The text was updated successfully, but these errors were encountered: