We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
const a = () => { await b(); await b(); }; async function b() {}
Run the auto-fix on save.
You'll end up with this invalid code (multiple asyncs):
async
const a = async async () => { await b(); await b(); }; async function b() {}
I tried fixing it with ts-fix and it seems to work fine and add only a single async keyword.
ts-fix
Using the function keyword, however, works fine:
function
// original function a() { await b(); await b(); }; async function b() {}
// auto-fixed async function a() { await b(); await b(); } async function b() {}
When cmd+zing, I get an invalid code that contains 2 async keywords, which probably means that it's being fixed in 2 passes?
cmd+z
The text was updated successfully, but these errors were encountered:
This issue seems to occur due to a bug in VS Code's auto-fix mechanism, possibly caused by a two-pass fix or conflict with ESLint/Prettier.
"editor.codeActionsOnSave": null
eslint --fix <filename>
Sorry, something went wrong.
It happens to me even when all extensions are disabled.
mjbvz
No branches or pull requests
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
Run the auto-fix on save.
You'll end up with this invalid code (multiple
async
s):I tried fixing it with
ts-fix
and it seems to work fine and add only a singleasync
keyword.Using the
function
keyword, however, works fine:When
cmd+z
ing, I get an invalid code that contains 2async
keywords, which probably means that it's being fixed in 2 passes?The text was updated successfully, but these errors were encountered: