New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate update event into the update, soft remove and restore events #8398
Labels
Comments
7 tasks
LOL, did think that it will take a month or even more. Please, make a review. I'm not sure in some cases. |
Need some help with Chinese docs. |
@pleerock When the BeforeSoftRemove feature will release? |
It's already released in 0.2.42. |
@spotykatch thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
Separate update event into the update, soft remove and restore events.
The Problem
Soft remove and recover fire update event, so you have to send some data for subscribers to understand it is not an update. While listeners can't get the difference at all. So you have to do it like so
course i.e.
The Solution
Update events should be separated into the update, soft remove, and restore.
Considered Alternatives
OR some data should be sent to listeners and subscribers highlighting it's not an update.
Additional Context
So the problem is back compatibility. There are some repositories and tons of users that rely on the current functionality. I think it should be discussed.
Maybe there should be an option inside
ormconfig.json
Are you willing to resolve this issue by submitting a Pull Request?
The text was updated successfully, but these errors were encountered: