Why forcedeleting an already soft deleted model triggers a delete (and the related events) as well?

[Carnicero90]

"Deleting" an already deleted event seems quite odd to me, so I was wondering what's the reason behind that choice.

[macropay-solutions]

Because soft deleting is done via a trait that calls the normal delete on forceDelete with a flag forceDeleting true.

see this related situation:
#54733 (comment)

[Carnicero90]

I looked at the source code and I do understand how its implemented, my question was more about the "why", since it doesn't make all that much sense to me

[macropay-solutions]

Backwards compatibility for sure at the moment they introduced the soft deletes. A soft delete is still a delete.

[macropay-solutions]

Or even when you decide to start using soft deletes, and you already have logic on deleted/deleting, keeping those events also for softDeletes seems a good idea. Of course when you introduce the trait you have to go over all your deleted/deleting logic to see what needs to be changed.