You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all - I would like to express my gratitude for the phenomenal work you guys are doing here!
Is your feature request related to a problem? Please describe.
I'm working on an a Project where we're building an SDK generator that parses an OAS based Schemas (with a huge set of endpoints where the parameters have default values specified whenever possible), coverts them into the GraphQL Schema and than builds and exposes the GQL queries/mutations. For exposing the queries we're using the buildOperationNodeForField function.
Unfortunately even though our GQL Schema properly takes and captures default values from the OAS Schema specification, buildOperationNodeForField function ignores them when building queries/mutations, which degrade our DX significantly (for most initial use-cases where we would let our users quickly test generated operations W/O having to provide all argument values for queries/mutations if they have defaults already contained within the GQL Spec).
Describe the solution you'd like
It would be expected that if the GQL Specification Nodes already contains default values (for Queries/Mutations) they would also be taken into consideration and propagated to the output of the buildOperationNodeForField function.
Additional context
It would be expected that the output of the below buildOperationNodeForField fn call:
First of all - I would like to express my gratitude for the phenomenal work you guys are doing here!
Is your feature request related to a problem? Please describe.
I'm working on an a Project where we're building an SDK generator that parses an OAS based Schemas (with a huge set of endpoints where the parameters have default values specified whenever possible), coverts them into the GraphQL Schema and than builds and exposes the GQL queries/mutations. For exposing the queries we're using the buildOperationNodeForField function.
Unfortunately even though our GQL Schema properly takes and captures default values from the OAS Schema specification, buildOperationNodeForField function ignores them when building queries/mutations, which degrade our DX significantly (for most initial use-cases where we would let our users quickly test generated operations W/O having to provide all argument values for queries/mutations if they have defaults already contained within the GQL Spec).
Describe the solution you'd like
It would be expected that if the GQL Specification Nodes already contains default values (for Queries/Mutations) they would also be taken into consideration and propagated to the output of the buildOperationNodeForField function.
Additional context
It would be expected that the output of the below
buildOperationNodeForField
fn call:would match the following:
I would be more than happy to submit the PR for this feature.
The text was updated successfully, but these errors were encountered: