Disable field in mutation


Is there a way to disable a field for GraphQL mutations or specifically for the add or update mutations and still allow the field for search queries? This can be useful when we won’t want the GraphQL users to change the field (like., the field for created timestamp) but still want the users to be able to query and filter on this field.

The field can thus be populated using the @default directive (when it arrives) or via the lanbda function.


Hey @iyinoluwaayoola,

Did you see the @generate directive? @generate - GraphQL

Thanks @matthewmcneely, I know the @generate directive but it’s not allowed on the field level, which is what I need.

1 Like