David Gray
David Gray
Same applies to @canModel but also breaks on collections, because if the resolver returns `null` the call to Gate will always reject.
How did this come about? well, we have a field that may be null, but if it isn't, we need to check access against the model. It's valid for the/a...
> To clarify: In your example, the field with @hasMany is nullable. Are you talking about differences between handling an empty list or null there? I think it should most...
regarding `@canRoot` I remember why we're not using that now. It's legitimate for our resource to be null, let's say for example "Passport" a User may not have a passport....
1. `collection: [Field!] @hasMany` note the @hasMany, if you use @canRoot, you have no way to pass the object of the @hasMany to the Policy of the root, so you...
You're trying to solve for the wrong problem K0ka. The ticket is quite clear that the behaviour of the @canResolved acts differently between empty collections (via @hasMany) and singular resolved...
I'd argue that not returning an auth exception on an empty list when using @canResolved, exposes information. You now know there isn't a value. If there is a value it...