CRUD permission on fields? about graphql-genie HOT 2 CLOSED

Well graphql will error if you ever attempt to set a non-nullable field to null so that shouldn't be an issue.

Yup, some of the major reasons I have used is for instance users shouldn't be able to delete their username or email but maybe could delete other things off of their profile.

Or you may have a conditional field on a user isAdmin that only admins should be able to create a value for.

Generally create/delete field permissions tend to be things that you want to be possible if you are an admin or have some special permissions that are higher than the rest of the fields on that type.

This type of question I'm going to try to encourage people to ask on stack overflow (tag with graphql-genie)

from graphql-genie.

Got it, thanks!

from graphql-genie.