Ian Kleats

@johnymontana This idea was the generalization of a specific use-case in which I was interested: implementing fine-grained access control. After reading up on the GraphQL documentation, it seems there's a...

Your first question could be referring to a few things, so I'll try to hit them all. As it stands right now, the ACL function is specific to the CRUD...

I would agree with @cooperka that this is likely due to duplication of field names within the query. The solution proposed in the GraphQL [documentation](https://graphql.github.io/learn/queries/) is to use an alias...

I'm starting from a similar use-case (but with Discretionary Access Control features). I have some initial work to achieving this on [my own fork](https://github.com/imkleats/neo4j-graphql-js). It's still very much in early...

1) That's part of the trade-off involved with achieving a single round trip for authorization&data. It does not seem impossible to build in an additional background field (Boolean) into the...

I'm spit-balling here, so bear with me. What if... you moved the logic for querying/resolving the RDBMS data sources (through an exposed REST API or a second-level GraphQL layer, etc.)...