Allow ReadModels Marked For Deletion To Be "Unmarked" for Deletion

[WardenUnleashed]

My team is currently developing some functionality where we will "deleting" multiple aggregates within a Saga. In the case that a step within the Saga fails, we add a compensating "restore" event to essentially undelete it.

This works fine for Aggregates as we have a simple IsDeleted boolean.
However, when we try to update the read model's we start to run into a problem. Ideally we would like to avoid adding a IsDeleted property on our read model and instead mark the model for deletion via the context(making it easier to query the read models in the future).

However, it would appear that once you mark the Read Model Context for deletion, you can't unset it.

I would like to suggest this as a feature.

Additionally, provided this is something that would be acceptable to change; I would be willing to implement it to reduce the bandwidth on maintainers.

[github-actions]

Hello there!

We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days.
We consider this issue to be stale and will be closing it within the next seven days.

If you still require assistance with this issue, please feel free to reopen it or create a new issue.

Thank you for your understanding and cooperation.

Best regards,
EventFlow

[github-actions]

Hello there!

We hope you are doing well. We noticed that this issue has not seen any activity in the past 90 days.
We consider this issue to be stale and will be closing it within the next seven days.

If you still require assistance with this issue, please feel free to reopen it or create a new issue.

Thank you for your understanding and cooperation.

Best regards,
EventFlow