Changes/Stream API about lokijs HOT 5 CLOSED

Yes, this definitely sounds like an attractive feature.

from lokijs.

Maybe I can add a new changeEventEmitter for every collection, and when use Loki, consumers can set their own event function for every change event, just like:

var users = db.addCollection('user');
users.changeEventEmitter.on('insert', function (obj) {
    ***
});
users.changeEventEmitter.on('update', function (obj) {
    ***
});

from lokijs.

I have a draft implementation going which is quite similar to what you suggested. This is underway.

from lokijs.

1.1 released, closing this.

from lokijs.

The Changes API currently implemented is a great feature for syncing changes to the db at times when the API is invoked. However, the API does not push/emit any events to possible subscribers. Is this on the table to implement at any point in time? That is, something similar that @wxygeek mentioned in the post above?

There are many scenarios under which this is helpful. If application has a reasonable code separation, certain components that encapsulate collections are not aware of one another. However, actions on one can be performed to affect the other. This can be seen in a simple favoriting feature of something. It would be great to have the ability to sign up and listen for a change event in order to refetch or rerender the data.

from lokijs.