Some of the issues raised by Sonarqube are false positives. Eg: https://sonarcloud.io/project/issues?id=mediawiki-extensions-Translate&issues=AWuKiMSZZf_vcVxnjMey&open=AWuKiMSZZf_vcVxnjMey - this property is being used during serialization.
As per this very recent blog post there are three ways of marking something as a false positive
I prefer the Mark as false positive approach as that would keep the code clean and we would not have dependency on the tool in our code. This approach would probably require us to be added as team members in the organization.
The second approach approach would be to use @SuppressWarnings(‘sf:UnusedPrivateField’), but we will have to add these throughout the code.
The //NOSONAR approach is obviously not recommended, as this would not display any other code smells or bugs either.
So my question is, is it possible to be added as team members for the organization, or would you recommend that we go with the second approach?