|
|
|
|
|
by verdverm
1919 days ago
|
|
I'd be interested to see a graphql library that makes security trivial. Could you add some links? In my experience, securing nested assets based on owner/editor/reader/anon was rather difficult and required inspecting the schema stack. I was using the Apollo stack. This was in the context of apps in projects in accounts (common pattern for SaaS where one email can have permissions in multiple orgs or projects) |
|
This is also easy to do with self-written servers, maybe take a look at the metadata folder to get a gist of what Hasura would be doing behind the scenes (running a query and then checking the claim for the condition for the given field that permission wants to be requested for)
(Just a repo I started one evening, it doesn't do much but the concept of projects with owners and collaborators should work)