Suggest new features

New features Think the latest versions could be improved in some way ? Come see if your idea is already shared by others, and make more suggestions that you think could benefit the overall community (beyond your specific case). New rules Suggest new rules that could enrich one (or many !) of the <a href="">SonarSource code analyzers</a> .
About the Suggest new features category [Suggest new features] (1)
[Java] Indirect access to static member [New rules] (1)
[Java] Unlikely argument type for Collection methods using Object [New rules] (1)
[Java] Access to non-accessible member of nested type [New rules] (1)
GitHub Pull Request Review [New features] (8)
[Drupal] Namespace importing should be preferred over include/require functions [New rules] (3)
Support for Pull Request Decoration in SQ Developer Edition [Suggest new features] (4)
Docker Container for 7.3 [Suggest new features] (8)
Cover rules from Eclipse JDT [New rules] (2)
Pull request branches to include code coverage [New features] (20)
Allow enabling sonar rules for test sources [New features] (3)
Extenability of S2699? (Tests should include assertions) [Suggest new features] (2)
"Serializable" classes should use auto-generated version ids [New rules] (6)
Switch case range rule S3936 [Suggest new features] (1)
Jira integration with SonarCloud [New features] (2)
Curl SSL/TLS trust chain verification should not be disabled [New rules] (3)
Documentation: SonarQube Migration to New Server [Suggest new features] (1)
Please distribute APT/APK packages of the scanner [Suggest new features] (1)
Add the compatibility rules for upgrading PHP Code [New rules] (3)
Scala version in Sonarqube [Suggest new features] (2)
Rule S00107 "Methods should not have too many parameters" should consider Lombok annotations [New rules] (1)
Allow to use empty comments by default in TrailingCommentCheck rule [Suggest new features] (3)
C/C++ field naming convention rules for public/private, static, constant, etc [New rules] (2)
[Java ] "read(byte[],int,int)" should be overridden [New rules] (2)
JAXB Context rule for memory leak [New rules] (2)
JDBC drivers should not be registered via `Class.forName()` [New rules] (2)
[Java] optional.orElseGet(null) produces a null pointer exception [New rules] (2)
New rule suggestion: "Boolean" objects should be used in a null safe way inside of expressions [New rules] (3)
android.text.TextUtils.isEmpty methods should be hardcoded [New rules] (3)
I would like to have a project template [Suggest new features] (4)