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
Then I get an error because the Shield is running the deny rule on every field resolver of the query/mutation result. It works if I have the option commented out, but then am I exposed to not having rules checking the field resolvers? Can someone query/mutate a field directly by somehow bypassing the Query/Mutation type?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I am trying to understand how to properly utilize the
fallbackRule
. If I set it to the deny rule to only allow the specified operations:Then I get an error because the Shield is running the deny rule on every field resolver of the query/mutation result. It works if I have the option commented out, but then am I exposed to not having rules checking the field resolvers? Can someone query/mutate a field directly by somehow bypassing the Query/Mutation type?
Beta Was this translation helpful? Give feedback.
All reactions