My team use SonarQube 8.9.9 Community Edition and we’re trying to get a view of how big our codebase is across the various projects Sonar’s analyzing using its metrics.
The problem I’m facing is that while the metrics are easily recognizing all our Java/Typescript/HTML/XML/etc. files, it’s ignoring the properties files and CSVs that I’d like included in the numbers (they’re how we do a lot of important configuration).
I’ve been doing some reading and it sounds like each of Sonar’s supported languages is backed by an analyzer that’s responsible for both the static analysis of the files and pulling out any/all metrics, like the one for Java: GitHub - SonarSource/sonar-java: SonarSource Static Analyzer for Java Code Quality and Security. You therefore can’t just add the .csv or .properties file extension to an existing analyzer as it won’t match the formal language definition and applying Java syntax/semantics to a CSV file would cause issues.
Is that right? If so, is there some faux language analyzer out there that just basic metrics like line counts? My google-fu must be off today, as I keep ending up in holes about the Sonar properties file for configuring your parameters or exporting results as CSVs.
If anybody could help point me in the right direction I’d appreciate it,