Pay attention of @softDeletes in mutation directives

Is your feature proposal related to a problem? Please describe.

Currently implementation of update/upsert don't use enchanceBuilder(), therefore it is not possible to update soft deleted model, because without appending e.g. withTrashed model will not be fetched.

So it is not possible to do something like this:

extend type Mutation {
   updateAuthor(input: AuthorInput @spread): Author @update @softDeletes
}

Well you can use it, but if model is soft deleted, @update is not able to find the entity, as user reporter here

Describe the solution you'd like

So here is my question: Should we take care of soft deleted models in update/upsert?

In my application I currently disabled in UI the ability to edit entity, if it is soft deleted (it is actually in trash). What do you think?

Start by tracing the update and upsert mutation directive implementations and the referenced enhanceBuilder() behavior, then compare them with the @softDeletes directive. The issue needs an agreed answer on whether trashed models should be editable and corresponding tests before the work is considered done.