Verbose permission error

What’s your idea?

Present a more verbose explanation when permissions are denied.

What problem might it solve?

Currently, complex applications that do complex operations on multiple tables are difficult to debug on the permissions space because the API just provides a generic message.

To be able to do this, developers need to debug the complex mutations separately, and this can be really cumbersome.

Have you seen it somewhere else?


Any ideas on how you think it could/should work?

Provide a more verbose message on at least where the permissions failed or where the request was rejected.


+1 this would be really nice.

See the generic error a lot when developing. Especially since the roles changed to not have any permissions to new tables by default.

1 Like