validated-method | Meteor methods with better scoping | Web Framework library

There is one thing to know about check and strings which is, that it accepts empty strings like '' which you basically showed in your malicious example.

Without guarantee to solve your publication issue I can at least suggest you to modify your check code and include a check for non-empty Strings.

A possible approach could be:

Optimistic UI works by running the method against the minimongo on the client to give you the most likely result from running the query on the server. Therefore the method needs to be available from both the client and server to enable optimistic UI.

If you want to do something differently on the client or server you have the isSimulation boolean that will be true in the case it is running on the client and false on the server side.

The relevant docs

validated-method has a built-in way of providing a context and it is documented in the README, exactly for cases like the one in your question.

method#_execute(context: Object, args: Object)

Call this from your test code to simulate calling a method on behalf of a particular user:

(source)

I found this issue,

'createUser' comes from 'accounts-password package' when you do : meteor add accounts-password

you can check in your application

/MyAPPLICATION/.meteor/local/build/programs/server/packages/accounts-password.js

we can find this :

Can you try replacing:

mdg:validated-method is doing fine. If you call (actually Meteor.apply) a regular Meteor method without introducing validated-method, the same result will be observed.

Here is the thing. In the documentation of Meteor,

The return value of the Method simulation is discarded, unless the returnStubValue option is passed when calling the Method, in which case it is returned to the Method caller. ValidatedMethod passes this option by default.

Notice the bold. In your example project, the returned object { finished: false } from simulation is the return value of the call, not the callback. Therefore, the following transformation of how you make the client call

OK, it appears as though I needed to also install collection2-core

meteormethod argument should call a Meteor.Method.

you should have define:

autoform treats required keys in the schema as being required in the form input which doesn't work for the _id key.

If you make the _id optional: true then your insert will work and Meteor will automatically insert the _id OR you can use a variation of the schema for the autoform which omits the _id key altogether: