Support custom repositories for the [[analyzer]] of Scan.toml

Abierto
#211 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
cli

Línea de trabajo

Start in ScanUtils.loadAnalyzer, where any repository value other than "local" is currently dropped, and look at how the generated dependency gets its repository field for the local case. Check how Settings.toml repository ids are read elsewhere in the tool so the same lookup can be reused. Done when an [[analyzer]] with a declared repository id resolves through that repository, and an unknown id fails with an error that includes its position. Ask in the issue how the repository id should be validated before you start.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Area/Configuration Type/New Feature
Area

Configuration

Problem

An [[analyzer]] in Scan.toml can only be resolved from Ballerina Central or, with repository = "local", from the local repository. Any other repository value is dropped without a message (ScanUtils.loadAnalyzer), so the analyzer is looked up in Central instead.

Ballerina supports custom repositories: a Maven repository declared in Settings.toml with an id can be used by a dependency through repository = "<id>" in Ballerina.toml. An organization that publishes its static code analyzer to such a repository can't use it with bal scan.

The release-readiness fixes for #190 make a repository other than "local" an error saying it is not supported, instead of dropping it.

Proposed Solution

Accept the id of a repository declared in Settings.toml as the repository of an [[analyzer]], and pass it to the generated dependency, as is done for "local". Report an unknown repository id as an error with its position.

Alternatives

Keep only Central and "local", and publish analyzers to Central.

Version

0.14.0

Lenguaje dominante
Java
Estrellas
15
Forks
12
Merge medio
2 d 8 h
PR fusionados (30 d)
29

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ballerina-platform/static-code-analysis-tool

Todos los issues de ballerina-platform/static-code-analysis-tool

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.