GraphQL API fails if custom type is not allowed via a field_policy
I noticed that if I ask my graphQL API to return a field that is forbidden, if the field is built-in, it will just return the field as
null
, all the other fields normally (assuming they are not forbidden as-well) and an error in the errors list telling that this field is forbidden.
But, if I try the same with a custom type, then I just get the full result as null:
5 Replies
What kind of custom type?
I have some custom types, but all of them have the same issue, here is one of them:
That’s actually very strange
I don’t see why that would happen
Field types don’t have anything to do with field policies
I will try to create a small reproducible project to help debug this
That would be great. A test in the ash_graphql test suite would be even better