Hi @stsenvidan,
I am truly sorry this update had such a negative impact on your teams.
We made the decision to make this change as an opt-out after considering the alternatives. The previous behavior has been a long-standing sore point for many users, particularly newcomers. They could not figure out why our analysis did not find other files by default.
Had we made it an opt-in, most people would forever have to include this parameter to activate this new behavior, which is not the experience we want them to have.
We made sure to implement this change in a major version so that people could review it before adopting it. Our policy has always been to follow semantic versioning for this very purpose. It allows us to move the product forward and sometimes make major (or even breaking) changes when necessary.
Finally, we included a warning as part of the analysis indicating this feature is now active and how to remediate problems if any arise. We are updating it to be clearer on the issue. This warning will be removed when most people have migrated to the new scanner and are aware of the new behavior.
That being said, if your projects experienced an extreme increase in their LOCs count, I would like to know what type of files caused it exactly. Is it actual code we were not analyzing before (which is the whole point of this update), or are we catching files we should not be analyzing (in which case, this is a bug, and we need to know about it so we can correct it ASAP)? We are aware of some instances where we unfortunately analyze coverage files as XML which is an unwanted behavior, and we are investigating a fix for that.
If you are seeing things being analyzed that shouldn’t, we could open a new thread so we can take a look at what’s happening in your projects, if you do not mind sharing some information with us. That would help us quash bugs quickly.
Denis