Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

$unset not working?

See original GitHub issue

I’m having a server side method with the following code:

let updateObj = (isTyping) ? {$set: {'profile.isTyping': 1}} : {$unset: {'profile.isTyping': ''}};
Meteor.users.update(Meteor.userId(), updateObj);

The problem is that redis-oplog doesn’t reflect that change, profile.isTyping is still available on the client side. redis-oplog sets it to null instead of removing it.

So I I do this on the client side:

 Meteor.users.findOne(this.foreignUser()).profile.hasOwnProperty('isTyping')

I will get always true, because the field isn’t removed. It works without problems on MongoDB + Oplog.

Issue Analytics

State:
Created 7 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

2reactions

theodorDiaconucommented, Mar 15, 2017

Oh my god. After squeezing my brains for 2 hours on this one I found it. When I’m overriding observeChanges I need to pass in a clone, not an object. Bc if I pass it as reference, publishComposite does not detect any changes here:

https://github.com/englue/meteor-publish-composite/blob/master/lib/subscription.js#L66

Nice bug. Solved. Will be available in 1.1.8 release

0reactions

theodorDiaconucommented, Mar 3, 2017

@dnish thank you for your detailed information. I have enough to fix.