Requesting inclusion in Marketplace - a3openapicore

SonarQube Server / Community Build Plugin Development
1

Hello SonarSource team,

We are API&AI Addicts community, and we would like to request the inclusion of our plugin a3openapicore in the Marketplace.

This plugin provides the core capabilities for analyzing OpenAPI specifications within SonarQube. Enables SonarQube to analyze OpenAPI specifications by providing parsing and core processing capabilities for OpenAPI definitions (YAML and JSON). It establishes the foundation for OpenAPI analysis within SonarQube and supports extensibility for additional rule sets.

The first release we would like to include is 1.1.1. Here is the information about the plugin:

We have prepared the data for the Marketplace. Here is the related Pull Request in the sonar-update-center-properties repository: PR

Thank you!

4

Hey,

Thanks for the submission!

I just tested both plugins together (the core and custom), things are looking good, but I am not sure if it impacts the built-in Yaml analysis. I will check that further and get back to you in 2-3 weeks (I will be off).

5

Hi Elena, thanks for your feedback!

Just to clarify, when you mention an impact on the built-in yaml analysis, could you please elaborate on what kind of impact you are referring to?

For example, do you mean conflicts with the default YAML analyzer, duplicated analysis, or changes in its behavior?

Thanks in advance!

6

Hi,

I am mainly concerned about conflicting definition of the language for the same file.

7

Hi Elena, thanks for the clarification.

We’ll be monitoring this closely while we wait for your updates. We are very interested in ensuring a smooth integration, so we’ll be on the lookout for any findings you might have to address them promptly.

Best regards!

8

Hey,

After a second look I realized that in your example project you reconfigure the defaults extensions for YAML language (standard language provided by Sonar).

sonar.lang.patterns.yaml=**/*.yml
sonar.lang.patterns.openapi=**/*.yaml

If those are not set, analysis will fail with following error:

15:15:10.078 ERROR Language of file '...' can not be decided as the file matches patterns of both sonar.lang.patterns.yaml : **/*.yaml,**/*.yml and sonar.lang.patterns.openapi : **/*.yaml,**/*.json

We can’t admit a plugin declaring a language clashing with a standard language provided by Sonar. I assume same goes for json files and JSON language.

I see the only workaround for you to not declare any new language and rely on standard Sonar language (JSON and YAML) to get files to analyze.

(Note that it’s still ok to declare a separate rule repository with whatever name you like)