be able to disable the 'This may be converted to an async function' tooltip

[AlexGalays]

Can we have an option to specifically disable this "hint"? Not everyone find the async function style superior. I'm never going to use this refactoring so it just hinders the readability of my files compared to previous versions of vscode.

[mjbvz]

Set "javascript.suggestionActions.enabled": false or "typescript.suggestionActions.enabled": false to disable these

[arenddeboer]

I also favour promises and simply disabling all suggestions feels rather heavy handed.

[AlexGalays]

yes, the granularity is too coarse here.

[joshburgess]

Many people don't find async/await to be superior in any way. This should be configurable on its own.

[trusktr]

Async is superior (IMO). :)

But still, for a function that manually returns a promise but never uses the await keyword anywhere in it's body, this tip is pointless. There's absolutely no reason to convert a non-await-using function into an async function. This tip should only appear (as an error) if we try to use await in a non-async function.

[alanxone]

Totally agree with @trusktr.

Disable the suggestionActions (JS/TS) is not the right way for us, since these two options control all diagnostics of JS/TS.

[AlexGalays]

Async is superior (IMO). :)

But still, for a function that manually returns a promise but never uses the await keyword anywhere in it's body, this tip is pointless. There's absolutely no reason to convert a non-await-using function into an async function. This tip should only appear (as an error) if we try to use await in a non-async function.

Let's not make it a discussion about which style is superior; I just wanted to illustrate that not everyone like the async style more than the explicit Promise style with a personal example.

vscode should be completely unbiased regarding coding practices. So either remove that half baked hint completely, or provide an option to toggle it in/out.