Hooks trigger changes about meteor-collection-hooks HOT 5 CLOSED

If you're getting a change event, there's something else at play here because collection-hooks doesn't fire two operations -- in fact it's just wrapping the original insert and firing off these callbacks before and after. Are you doing an upsert perhaps?

from meteor-collection-hooks.

It is a regular insert. I made a sample app to illustrate what I am talking about.

https://github.com/cbelsole/meteor-insert-hook-test

from meteor-collection-hooks.

That's latency compensation at work... You're only setting up the hook on the server, so the behavior makes sense. Try removing the server conditional around the hook.

from meteor-collection-hooks.

I see. When it tries to write to the client (added) and then syncs with the server. At the server it adds the information to the document and then syncs back with the client (changed). Thanks for helping me figure that out.

from meteor-collection-hooks.

You got it :)

from meteor-collection-hooks.