(Cascade)-Delete Directive

Interesting for sure, but this makes me wonder where the line in the sand is for handling custom business logic. With a dozen developers there could be a dozen tweaks to this depending on the actual needs. So does this get extended to cover all those cases, or is it better for development to push stuff like this somewhere else? (Something like lambda but maybe an actual hook into the go rewriter from GraphQL to DQL—not an official request just me thinking out loud)

I would find such useful and for my use cases I would want to create a directive that normally hides soft deleted nodes and instead of showing them with a filter use something like @showDeleted