-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Don't trigger changes if nothing was actually changed #64
Comments
@Maxpain177 good find. yes it will be fixed. |
@Maxpain177 a lot of changes are currently required to do such a thing. Basically the current observe() is not a full implementation of the observe() which has support for addedBefore, etc. Do you really need this functionality ? This is my question. Because if there is no way to work-around this in some scenarios we will implement it. |
@theodorDiaconu Yes, In my project (which contains several microservices, connected to one mongodb and redis) it is using everywhere. |
@Maxpain177 I understand. Redis-oplog is now ready to go under some restructuring and refactoring, and this will be included :) |
@theodorDiaconu, Currently, i can't use this package, because i need remake most part of application architecture for working without oldDoc. |
@Maxpain177 check it now :) |
@theodorDiaconu Yes, it works. But, if nothing changed in doc, changed function still fires. |
@Maxpain177 can you give me an example ? What kind of update you do ? |
@theodorDiaconu Counts.update({ _id: "users" }, { $set: { count: 0 } }) |
@maxnowack so if "count" was previously ZERO, it should not fire the change event. |
Fixed. |
oldDoc not passing
It's possbile fix it?
The text was updated successfully, but these errors were encountered: