Schema documentation and Client-side logic about graphql-shield

[maticzav]

Hey, I thought I already replied to this, sorry for the delay. I love your idea! Unfortunately, we entirely rely on graphql-middleware. I think it would be possible to do some auto-generation which could turn out really cool, but I am not so sure about the description idea. It is possible, but I think we should find a bit more use cases to add such functionality to grpahql-middleware.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Victordmdb]

Hi, I'm curious if there's a simple way to determine if the user has permission for mutations from the client? Or would it require an introspection query?

[maticzav]

@Victordmdb I am not sure I understand your question. From what I know, neither of the two would give you that information. One way I can imagine obtaining such information would be by forwarding a role in user's session information. That, however, would have to be determined by the business logic of your application, not the schema.

[Victordmdb]

@maticzav I'm testing out CASL which fits well with graphql-shield to handle permissions at every level.

[veeramarni]

@Victordmdb Will you suggest to use CASL based on your testing?