`reject` option about execa

[sindresorhus]

Are we having it as a parameter so that we can control this functionality?

Yes, read the issue title.

Maybe just {reject: false}.

[mbad0la]

Why can't we use the catch method upon rejection of our promises? That can be used to display results such as linter issues. Am I missing out on something?

[sindresorhus]

@mbad0la That works, but it's more verbose when using async functions as you need to wrap it in a try/catch. Example:

execa/test.js

Lines 26 to 30 in 9345d2c

	try {
	await m('./fixtures/error-message.js');
	} catch (err) {
	t.true(err.message.indexOf('stdout') !== -1);
	}

[mbad0la]

@sindresorhus I get it and I do support this functionality. Are we having it as a parameter so that we can control this functionality?
Btw, What do you think about the name overrideReject? Personally, the rejection is not an error as we might get our desired behaviour through catch as I mentioned earlier. So having the word Error in the option is maybe not that correct. What do you think about this?

[mbad0la]

My bad, sorry about the question. reject works with me.