Dear @i18ncraig,
Is the solution I suggested acceptable for you?
If you prefer to contribute those rules directly to SonarJava we can go over the list of rules you would like to add. This is a case by case process where we evaluate the number of false positives each rule would raise and how we can improve the rule to make it valuable for every developer.
In the slides you provided I see only one example of non-compliant code.
It would help us if you could provide for each rule:
- a description of the rule
- a non compliant code example
- a compliant code example showing the fixed code (if applicable).
If there are many rules I suggest to create one post per rule in this section of the forum. You can ping me in each post by writing @Nicolas_Harraudeau.
Here is an example of such post.
We are currently fully focused on the next SonarQube LTS version. As I don’t want to keep you waiting a long time for an answer, I suggest to start this process after the LTS release, i.e. in June.
Let me know if this solution or the previous one is ok for you.
Cheers,
Nicolas