You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add a new field of languages we analyze to the plugin manifest, so the plugin is downloaded from SonarCloud only when needed. See work done in https://sonarsource.atlassian.net/browse/SC-8970
Identified languages (to be confirmed) : js, ts, css, web, yaml
This should be only added after sonar-security adds the subset of languages to their plugin otherwise, sonar-security can fail on runtime because it depends on sonar-javascript plugin.
Also note that in the SonarCloud ticket they assume that file property is called “_sonar.{languageKey}.file.suffixes”_,, which is not true for our plugin. The language key is js or ts, while the property is sonar.javascript.file.suffixes or sonar.typescript.file.suffixes respectively. This should be clarified with SonarCloud team
The text was updated successfully, but these errors were encountered:
We should add a new field of languages we analyze to the plugin manifest, so the plugin is downloaded from SonarCloud only when needed. See work done in https://sonarsource.atlassian.net/browse/SC-8970
Identified languages (to be confirmed) :
js
,ts
,css
,web
,yaml
This should be only added after sonar-security adds the subset of languages to their plugin otherwise, sonar-security can fail on runtime because it depends on sonar-javascript plugin.
Also note that in the SonarCloud ticket they assume that file property is called
“_sonar.{languageKey}.file.suffixes”_,
, which is not true for our plugin. The language key isjs
orts
, while the property issonar.javascript.file.suffixes
orsonar.typescript.file.suffixes
respectively. This should be clarified with SonarCloud teamThe text was updated successfully, but these errors were encountered: