go.lintOnSave description is confusing

[Zyl9393]

Is your feature request related to a problem? Please describe. Something happened after installing Go 1.18 to drive Microsoft Defender's Antimalware Service Executable nuts every time staticcheck or such is invoked, resulting in audio choking and other such things which make Linux users sigh in pity. I noticed I can disable this with setting "go.lintOnSave": "off" while Microsoft's cloud security learns of these newly built binaries to eventually fix the problem. Thereby I encountered the setting's description:

Describe the solution you'd like Write an actual explanation regarding how the options other than "off" are different from each other. What am I actually setting here?

Describe alternatives you've considered Make the educated guess that this setting decides the scope of what gets linted, even though its description fails to expressively say so.

[hyangah]

The followings are defining the scope and implicitly enabling linting on save.

• file -> lint the current file on save
• package -> lint the current package on save
• workspace -> lint the current workspace on save

The following disables linting on save.

• off -> disable lint on save

PRs on the description in package.json are welcome! Make sure to run go run tools/generate.go -w after updating the doc. Thanks!

[keremgocen]

happy to take on this