Support disabling rules via //NOSONAR about aem-rules-for-sonarqube HOT 5 CLOSED

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. #230
Contributions are welcome. Let's continue the conversation there.

from aem-rules-for-sonarqube.

Hi @kwin,

thanks for the ticket, it makes much sense. Is this something you'd like to contribute or you're willing to wait as I will need to find volunteer internally?

from aem-rules-for-sonarqube.

Hi @kwin i've just checked this issue since the NOSONAR wildcard is supposed to work with any issue raised, from wherever the issues come from. Info

I've done some quick test by self check rules project code and this issue was properly igonred.

from aem-rules-for-sonarqube.

I have tested the NOSONAR comment below on the line of code reporting an HTL issue. The comment below does not suppress the Sonar Error. I am able to suppress HTML issues however.
<!—/* //NOSONAR */—>

from aem-rules-for-sonarqube.

@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.

from aem-rules-for-sonarqube.