Hello @Marco_Comi, thank you for your reply.
which IDE are you using SonarLint with?
I am using SonarLint with Visual Studio and Visual Studio Code.
which programming language(s) are you coding with?
what is the main reason you would like SonarLint to propose and apply fixes?
The main reason would be to save time. I don’t have exact numbers, but we do have projects with over 9k code smells (that’s something for another discussion…) and in an enterprise environment like ours with hundreds of projects, we’re talking about many man-years to solve them all.
what is your expectation exactly
If we’re talking about saving time, then SonarLint would ideally automatically fix issues where possible. This could be on demand, on save, on build. I would probably prefer on demand for an entire project (or: solution if we’re talking Visual Studio). An Undo function could be helpful, then again we have source control for that. Manually trigger fixing individual issues would only marginally contribute to saving time so that would not be my first intention.
Perhaps spotless that I use for Java projects may be a good example of what I am thinking about.
What it exactly should and shouldn’t automatically fix is up for debate I guess. Removing unused imports/usings seems trivial, so are simple things like writing hex color values in lower case in css. Formatting parentheses, indentation, newlines… Other things like making private member variables final/readonly might prove to be less trivial. And there are certainly things that could/should not be fixed automatically. But starting with low hanging fruit, it could save a lot of time and thus costs.