Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support disabling rules via //NOSONAR
See original GitHub issueAEM rules should be possible to disable with the Java comment //NOSONAR (similar to what is possible with the Java Plugin). This currently does not work.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Support disabling rules via //NOSONAR · Issue #78 - GitHub
AEM rules should be possible to disable with the Java comment //NOSONAR (similar to what is possible with the Java Plugin).
Read more >Ability to disable specific Sonar rules on specific lines of code?
So, I'm kind of leaning towards some kind of NOSONAR approach, but if it can be figured out how to support this with...
Read more >How do we avoid developers to use NOSONAR / Avoid ...
Hi Team, How do I avoid developers to bypass SonarQube rules using NOSONAR as mentioned in the SonarQube documentation - FAQ it will ......
Read more >How to disable Sonar rules for specific files? - Stack Overflow
csv file containing all the rules' keys. I'm using SonarQube version 4.1.1. Share.
Read more >Configuring a Project to Exclude Certain Sonar Violations
We can disable a single line of code by putting a //NOSONAR at the ... We can get the rule identifier using the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @bhartm3, @chutch is no longer involved in maintaining the project. I believe the original issue pertained to Java rules, which seem to work as expected. HTL support was introduced in 2019, after this issue was raised and closed. I’ve opened a separate issue to test/implement NOSONAR comments in HTL code. https://github.com/wttech/AEM-Rules-for-SonarQube/issues/230 Contributions are welcome. Let’s continue the conversation there.
@chutch the comment of @garbacikp is not correct as @boobootoo2 mentioned. The functionality must be implemented for the HTL rules itself. Can this feature request be reopened as its still valid. We may volunteer if we get some time soon but currently we are in the AEM upgrade process.