Don't trigger changes if nothing was actually changed about redis-oplog HOT 12 CLOSED

@Maxpain177 good find. yes it will be fixed.

from redis-oplog.

Fixed.

from redis-oplog.

@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.

from redis-oplog.

@theodorDiaconu Yes, In my project (which contains several microservices, connected to one mongodb and redis) it is using everywhere.

from redis-oplog.

@Maxpain177 I understand. Redis-oplog is now ready to go under some restructuring and refactoring, and this will be included :)

from redis-oplog.

@theodorDiaconu, Currently, i can't use this package, because i need remake most part of application architecture for working without oldDoc.
Thanks 👍

from redis-oplog.

@Maxpain177 check it now :)

from redis-oplog.

@theodorDiaconu Yes, it works. But, if nothing changed in doc, changed function still fires.

from redis-oplog.

@Maxpain177 can you give me an example ? What kind of update you do ?

from redis-oplog.

@theodorDiaconu
Just updating document.

Counts.update({ _id: "users" }, { $set: { count: 0 } })

from redis-oplog.

@maxnowack so if "count" was previously ZERO, it should not fire the change event.

from redis-oplog.

@theodorDiaconu, Reproduction

from redis-oplog.