_execute not passing down context to nested ValidatedMethods

[workflow]

First, thank you for this highly useful package! 🎉

I have the following situation:

One ValidatedMethod (on the server) A is calling another ValidatedMethod B (again on the server only).
Now if I _execute() the outer method A and pass it a userId context, that userId gets lost in the inner method B, and userId is again undefined.

Reproduction

https://github.com/workflow/validated-method-repro

Outcome

I20170425-21:29:03.151(2)? Outer method userId:  fXHHHMYTzzk3i4eKf
I20170425-21:29:03.152(2)? Inner method userId:  null

Desired

I20170425-21:29:03.151(2)? Outer method userId:  fXHHHMYTzzk3i4eKf
I20170425-21:29:03.152(2)? Inner method userId:  fXHHHMYTzzk3i4eKf

The only workaround I've found so far is to _execute B instead of calling it, explicitly passing down the userId. Not very pretty, since this affects production code to make the tests work.

[Paul-Vandell]

Hey there, i think that you find the best solution to get the userId context. _.execute is used for test but in this case maybe it was the right way

[MastroLindus]

Just found this one out for me as well.
For the moment I also switched those "call" invocations to "_execute" but it looks and feels dirty to me as well (production code shouldn't have to change because of tests)

[chmelevskij]

Ended up doing a similar thing. But instead adding Meteor.isTest check to decide between call and _execute

[jirkadev]

Maybe someone can change the _execute function so it would pass down the context.
This is the code @chmelevskij mentioned above.

if (Meteor.isTest) {
    myValidatedMethod._execute({ userId: this.userId }, { myArg })
} else {
    myValidated.call({ myArg })
}