Hello @ganncamp. Thanks to this post SonarCommunity Roundup, April 11 - 17 I found out the issue was created Jira .
What I’d like to add is that:
-
We don’t use Ruby in our project so this is unlikely a cause of the UI issue I reported
-
However we do use import of 3’d party rules like ESLint/Stylelint which may contribute values that are currently not processed well by UI.
Should this issue be fixed on UI instead of fixing the Ruby analyzer to cover wider set of cases?