Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Open
Description
Before You File a Proposal Please Confirm You Have Done The Following...
- I havesearched for related issues and found none that match my proposal.
- I haveread the FAQ and my problem is not listed.
Description
Inthe documentation for the@typescript-eslint/return-await
rule, it says that using "in-try-catch" as opposed to "always" is purely a stylistic concern.
However, onthis mdn page, it explains in the "Improving stack trace" section that using the "in-try-catch" style results in a worse stack trace. Thus, if true, this isnot purely a stylistic concern.
Is this accurate? If so, it seems a compelling reason to use "always" instead of "in-try-catch", and I propose that:
- the documentation for the
return-await
rule should be updated to reflect this and - the default option should be updated for all users of TSESLint.