esql:NavigatingTreeCouldBeReference - Rule Behavior Issue

Hi,

We recently upgraded to Sonar Server 7.9 and along with that upgraded the sonar-esql-plugin from 2.3.5 to 3.0.1. However, after this upgrade, projects for which we had clean reports started showing major issues after re-run with the "**Navigating message tree could be replaced by a reference**" Rule. (We have classified this as a major rule and we have build breakers in place with a threshold of 0 for this).

The behavior seems off as it reports major issue if the occurrence of two level tree structure is more than 3. For the following case, it seems to be not applicable -


There is no other way in our knowledge that we can create a reference for XMLNSC.Attribute.

Also, in case of the compliant solution, if **reqRef.age** occurs more than 3 times, it will be reported as an issue.


This default threshold however seems to be unchanged compared to the earlier version. So, the behavior of rule has changed it seems.

Please suggest if this is working as expected or needs an enhancement.

Thanks.