Rules with specification (RSPEC) but not implemented yet... any way to know if the rule is going to be implemented?

Hi all!

I was just checking the rule specification repository at:

And I found that there are “active” rules specification that are not implemented yet.


Everything seems to be defined but the rule is not yet in Java repository.

The specification for the rule was created on June, 2015.

There are other examples in the same situation:

Is there any way to know if the rule will be implemented or not?

Thank you very much for your help!


Well spotted! In fact we have a number of old specifications. Some of them seemed like a good idea at the time, and some where specified ahead of their time. That is, we knew we wanted the rule some day but didn’t have the tech in place to implement it.

You can see what’s queued for implementation by watching the issues repo (typically Jira, but GitHub Issues sometimes) for the language in question.

BTW, you may be interested to know that we’ve migrated away from that Jira repo. The live repo is here: GitHub - SonarSource/rspec: Rule Specification

Are you specifically advocating for those three rules, or is this a general question?


1 Like

Hi Ann!

Thank you very much for your quick response! The new Github for rule specification is amazing! Thanks!

I was interested on those rules because they replace old rules from PMD that are active in our profiles, and it will be great if they are implemented. We want to stop using third-party analyzers but there are still rules that are not available in SonarQube analyzer.

Just to let you know in case you can “prioritize” the new rules:

Those are the remaining rules from our older profiles that should be implemented in order to finally remove the third-party analyzers. Just a few rules that will make us very happy.

Thank you very much for your help!

1 Like