should mention throwStubExceptions in error handling part of methods section
irrigator opened this issue · 2 comments
I just learned that the validated-method package turns on the throwStubExceptions option of Meteor.apply, which stops the server-side method from being called if an error was thrown by the client. What's more, "if you have some permission logic that relies on data only available on the server, you should wrap it in an if (!this.isSimulation) { ... } statement."
I think this is a very good pattern, which not only conserves server resource but also forces you to make clear what kind of errors can be determined on the client and what can only be determined on the server.
It might be a good idea to add this pattern to the error handling part of methods section. Its not being there may cause confusion.
You're right! Going to add it now.