JS custom rules obsoletes since Sonar 8.9

[Ella-dee]

Hi,

In the "To do - Work-package GreenCode" in https://github.com/cnumr/ecoCode/projects/1, there are several Javascript rules.

However, as mentioned here https://github.com/SonarSource/sonar-custom-rules-examples/tree/master/javascript-custom-rules, custom rule support was removed in SonarQube 8.9 LTS and as a replacement, we are encouraged to have a look at ESLint, it provides custom rules that wecan then import thanks to the external issues feature.

Shouldn't those "To do Js Rules" be replaced by ESLint rules?

[glalloue]

Thanks @Ella-dee
We didn't have this information and it's an important point to notice.

If javascript rules are supposed to be managed by ESLint maybe we have to get out the javascript rules from ecoCode and to move them to https://github.com/cnumr/ecoLinter project.
ecoLinter is a part of ecoCode project but only with focus on linters (JS and CSS) and with a different project because it's not based on plugin behaviors.

We can suppose that the ecoCode challenge and especially the members of "Work-package Greencode" group can also push some modification to ecoLinter project.

@jules-delecour-dav & @olegoaer : what do you think about it ?