Latency Compensation

[veered]

I am modifying the modifier passed into a before.update hook and noticed that these changes are being passed to the update hook on the server. So the client and the server aren't processing the same modifier; the server only has the modifier outputted by the client side hook. This is related to the discussions here https://forums.meteor.com/t/meteor-collection-hooks-confused/748/7.

The solution on the forum is to wrap all update calls in a Meteor method, which gives us the usual latency compensation. Unfortunately this isn't an option when using an external package (like Autoform). Is there any other way to get proper latency compensation with this package?

[ThaumRystra]

Unfortunately this isn't an option when using an external package (like Autoform).

This is still an option when using autoform, see the autoform docs on using methods. Autoform can call a Meteor method instead of calling the update function itself.

[zimme]

I'll try and add a note about this in the docs.

I'm also thinking that an option to change the current behaviour to the expectation in this issue, would be nice.

[StorytellerCZ]

For the documentation part, it looks like duplicate of #65