Settings web page with custom language plugin

[gquerret (Gilles Querret)]

Hello,

My plugin for a custom language contributes properties, which are visible in the Settings web page. However, they are not displayed in the “Languages” section, but in their own “OpenEdge” section:

Properties are defined in the main plugin class like that:

    context.addExtension(PropertyDefinition.builder(Constants.SKIP_RCODE) //
      .name("Skip rcode parsing") //
      .description("Don't parse rcode in the build directory and from dependencies") //
      .type(PropertyType.BOOLEAN) //
      .onQualifiers(Qualifiers.PROJECT) //
      .build());

I’ve tried playing with the category and subcategory methods, but that didn’t change anything. I also had a look at the sonar-xml plugin, but properties seem to be defined in the same way. And they are visible in the languages section.

What should I do to have the OpenEdge properties in the Languages section ? Or is this section reserved for the SonarSource plugins ?

Thanks
Gilles

[Scott]

Hello,

The language list is hardcoded to include only the plugins maintained by Sonar, as seen here: sonarqube/server/sonar-web/src/main/js/apps/settings/constants.ts at 4cd56b34a6bb874a879d425299d52284ae32010f · SonarSource/sonarqube · GitHub

Unfortunately, it appears that Sonar doesn’t want third-party plugins to have the same level of integration with the SonarQube platform as its own plugins.

[gquerret (Gilles Querret)]

Thanks Scott !

Dear SonarQube dev team, would it be possible to have those properties in the same location? I think it’s more confusing to have them as top-level entries rather than in the languages section.