Hm, there are three problems in this case.
The first is that these tasks based on reverse or similar would be very expensive. It would have some impact on performance.
The second point is that it is somewhat dangerous to do automated deletions. There are several deletion situations that are out of control. So it is better for the user to decide what to do.
The last is that the deletion would have to execute a query internally to collect the reverse UIDs. Technically they are two distinct procedures and there is no such support in Dgraph - which merges both.
Sure, it’s possible, but it needs to be evaluated. If you are interested please fill out an Issue in Github following the logic of experience report.
Cheers.