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
We would like to define client fields in node_modules, and have those seamlessly work with our existing codebase
Each client field is defined according to some schema. The schema can't be global.
There needs to be some notion of compatibility between the schema used by a given client field and the schema where we are using the client field. And there can be some notion of transforms.
So, e.g. you might have a client field that expects a full_name field to exist (this is the client field schema). And you might be using it (i.e. root schema) in a world where first_name and last_name exist.
We should be able to say that to transform the client field schema to the root schema, use a client field full_name: data.first_name + data.last_name.
This concept should (of course) be independent of GraphQL.
Anyway, this obviously needs work.
The text was updated successfully, but these errors were encountered:
So this implies that in our own codebase, there shouldn't be a global schema.graphql, but instead it should be discovered? And specific to a particular folder? Idk
We would like to define client fields in node_modules, and have those seamlessly work with our existing codebase
Each client field is defined according to some schema. The schema can't be global.
There needs to be some notion of compatibility between the schema used by a given client field and the schema where we are using the client field. And there can be some notion of transforms.
So, e.g. you might have a client field that expects a
full_name
field to exist (this is the client field schema). And you might be using it (i.e. root schema) in a world wherefirst_name
andlast_name
exist.We should be able to say that to transform the client field schema to the root schema, use a client field
full_name: data.first_name + data.last_name
.This concept should (of course) be independent of GraphQL.
Anyway, this obviously needs work.
The text was updated successfully, but these errors were encountered: