Closed ducquang92 closed 2 years ago
Thank you for pointing this out. I was not previously aware of this issue. Probably our first step needs to be to inform the SonarSource team. They may want to deconflict on their end. Either way they’ll have good advice on how best to negotiate through this. I’ll try to start that conversation with them in the next few days and will post a link to that here.
Request posted. I'm looking forward to hearing their perspective.
Please try out release v2.2.0. Let me know if that doesn't fix things for you.
As always, be sure to back up your database beforehand and test the upgrade in a non-production environment to verify that your custom rules survive the upgrade.
Hi, After upgrading to SonarQube 9.3.0, the plugin cause the following error:
Apparently there is a new build-in feature with the key "text" in the new version, so it causes the key conflict. Could you please look into how to fix it?