runParsed Callback #3
Description
Hey Blockspring Crew,
The callback for the runParsed method currently provides one argument res for both error and success.
Best practice has a callback provide two arguments, an error and result, in that order. If a user wants to use any Async wrapper on the method (see here for example), the atypical callback arguments become a headache.
Thoughts?