(Cascade)-Delete Directive

[maaft]

@amaster507

I wouldn’t use the @showDeleted directive on the schema only on client requests. Just a quick hack that doesn’t require another JWT and doesn’t need to conflict with existing filter logic. Having a complex filter in place it could remain the same with just throwing in this directive as needed.

Sorry, I think I didn’t express myself correct. You wouldn’t need JWT to achieve your requested @showDeleted behaviour right now. Adding @auth(query: {rule: "query {queryFoo(filter: {not: {has: deletedAt}}) {deletedAt}}"}) to your queries (and setting the flag with update) would be sufficient. Of course you could just omit this directive when instead you want to allow queries on deleted objects.

Edit Sorry, I missed the part where you said that you want @showDeleted on client-side. My bad.

@amaster507

Again not sure if this is the best way to handle all of these business logic cases. I would be interested to know if other graph databases support features like this from the schema side. Or do they provide any sort of hook like business logic? The main difference is probably going to lead to the fact that they serve servers that create API layers where dgraph removes the need for an API layer and serves clients directly

I’m also not aware of any graph-databases but I have seen pre- and post-hooks in prisma-nexus (SQL schema → GQL Crud API generation). See: feat: support custom resolvers by craigspaeth · Pull Request #674 · graphql-nexus/nexus-plugin-prisma · GitHub