canceling a subscription

[chisholmd]

any ideas on an unsubscribe?

[chisholmd]

Ok I have a halfway workable solution:
on subscribe I return the index of the new entry in the callbacks array
then I pass it back to a new unsubscribe method the makes that entry null.
then in processCallbacks I just skip the nulls.

The callback array will continue to grow tho :( needs to be a better way.

[chisholmd]

ok will a bit better again.
in beedle I maintain an incrementor and store that will the callbacks. So the array now has objects instead of just anonymous functions.
{idx: incrementor, callback: callback}
when I add a subscriber I return the idx and then pass it back to unsubscribe and remove the array element.
So the incrementor might become a larger number in a really really long session but I doub't it would pass the limit of nine quadrillion

[hvdmeulen]

In my implementation of this nice Beedle store, I added unsubscribe functionality, inspired by Redux unsubscribe:

In the subscribe function, instead of returning true, return an unsubscribe function. Add this to the subscribe function:

const callbacksForUnsubscribe = self.callbacks;

// Return a function to unsubscribe the callback
return function unsubscribe() {
    const index = callbacksForUnsubscribe.indexOf(callback);
    callbacksForUnsubscribe.splice(index, 1);
}

Now you can unsubscribe like this:

// subscribe
const unsubscribe = store.subscribe(callback);

// unsubscribe
unsubscribe();

Seems to work just fine.