AccsoSG

Hi @darrellwarde , Thanks for the feedback. Feel free to rename the issue.

Recently I encountered a similar problem when defining roles in authentication. We currently define the roles as string values, but that's not really a good thing. This can lead to...

@darrellwarde Sorry for the late reply. For example, I declared a type with the following auth rules: ````gql extend type FormatFamily @auth( rules: [ { roles: ["ReadOnlyUser"], operations: [READ] }...

I'm also waiting for such a feature. In our project this is one of the biggest topics of discussion. Recently I came up with the following idea/workaround based on the...

@litewarp thank you! Are there any examples of using this Tools with neo4j graphql?

Isn't that already possible with the callback directive?

Hi @MacondoExpress, Thanks for the answer Is there currently a workaround to do this in a single mutation?

@tbwiss We are currently not affected by this issue in our project. Anyway thanks for the workaround 👍

We encountered the same problem in our project. How @tanahel-udem said, the performance problems probably come from wrapping all implicit (default) resolvers, even if no rule is defined for them....

Hi @Liam-Doodson Thank you for your answer. But if I remove Connect/Disconnect, then I can no longer set this relationship in a Create-Operation, can I? ````graphql type Identifier { value:...