Are sonar rules too strict for logic-heavy string handling?

Quick question for the group — has anyone noticed sonar flags increasing for small logic-heavy loops or string handling even when the code is clean and readable? I’m seeing warnings that feel a bit over-aggressive in projects with lots of word validation and scoring logic, similar to patterns used in a spelling practice game built for quick rounds.

It makes me wonder: how do you usually balance rule strictness vs readability in these cases, and are there specific rules you tend to suppress for this kind of logic?

Hi,

Welcome to the community!

Could you share what language(s) you’re experiencing this in? And also what version of SonarQube?

 
Thx,
Ann