VSCode feature request: option to disable codeAction on save

[Meligy]

Sometimes Sonar can be slow.

Sometimes you can’t do anything about it. Maybe it’s your own internet. Maybe it’s a connected server not Sonar cloud, and the server is having issues. It could be many things.

Right now, the only way to turn off Sonar on save without disabling the extension completely, is to disable all code actions.

But you might not want to disable the other tools.

So, my request, is to add a new property to turn off just the Sonar code action.

Similar to other linting extensions do, for example:

"editor.codeActionsOnSave": {
	"source.biome": "explicit",
	"source.fixAll.eslint": "always"
}

It would be great if I could also have source.sonar in this list please.

Thanks a lot.

[sophio.japharidze]

Hi there @Meligy, thanks for your post and welcome to Sonar Community!

We will soon release a feature that will allow you to disable automatic (on-the-fly) analysis of SonarQube for IDE. Do you think this would be helpful for the scenario you describe?

All the best,
Sophio

[kussberg (Edgar)]

@Meligy the latest version of the plugin now provides ability to disable automatic (on-the-fly) analysis. Let us know if that works for your use case.