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.
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