When withoutMongo, records still require an id, or they silently fail.

[ggn06awu]

Turns out when trying to tie in a pub/sub using withoutMongo: true, our messages never get sent out again to subscribers, yet a manual PSUBSCRIBE in redis on the same channel picked them up fine. We later discovered the cause was not having an id on the original message object.

The offending line from observe-changes.js:

ids = !message.id || _.isArray(message.id) ? message.id : [message.id];

I've made an id from our specific use case, but can we please add some validation and / or remove the requirement for an id (object hash + timestamp + rand() ?) in this scenario please?

[artpolikarpov]

Will think about it. Nice that you found a workaround.

P. S. I use withoutMongo:true option only with upsert and remove and I also add an hardcoded _id to the selector.