Allow to modify schema types easily? #95
Replies: 3 comments
-
Sounds like you need a few more transforms in or out of graphql-tools-fork and then create a yaml wrapper? Versus doing it all in mesh? |
Beta Was this translation helpful? Give feedback.
-
@yaacovCR I guess we'll use |
Beta Was this translation helpful? Give feedback.
-
Hi, had a thought about this, namely not really sure if adding transform to allow a subschema nonnullable field to be nullable makes sense, as underlying subschema is still not nullable, and so null will not be returned. The reverse seems to make sense. You might want fewer fields to be nullable than original subschema. This should be possible with existing generic TransformFields (TransformCompositeFields, TransformObjectFields, TransformInterfaceFields, TransformRootFields) but could always be made easier by putting out a specific non-null transformer like the FilterFields and Rename*Fields transformers do... Any suggestions for name? |
Beta Was this translation helpful? Give feedback.
-
Something like that:
This is mostly for modifying the schema, and changing fields behaviour, that are conflicts in any other way. So we cant do
extend type
and override those types.This goal behind this is to allow easy transformations.
Beta Was this translation helpful? Give feedback.
All reactions