Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[2.0] move domain-specific definitions out of `common` into their owning modules

Abierto
  • ¿Algo no está bien?
#1,135 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Área
backend-api-design

Línea de trabajo

Start by inspecting the common module and the named owning modules: cyclonedx, component, release-notes, and blueprint. Trace each definition's current references, including identifiableAction and the proposed heritage location, before moving anything. Done means domain-specific definitions no longer remain in common and all listed references and descriptions still resolve correctly.

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

Descripción

CDX 2.0 defect

currently, the common module contains things that belong to other modules.

  • base64 might be removed - it is not used anywhere 0 is this a mistake?
  • signatures is just an alias which should not exist in the first place
    • see #1133
    • see #1134
  • preDefinedLifecyclePhase shall be moved to cyclonedx - the only place where it is used
  • commit/diff/patch shall be moved to component - the only place where it is used
    • and also move the identifiableAction with it - it is only used there
    • maybe move to new module heritage? or to component#$defs/heritage/$defs?
  • issue shall be moved to release-notes - the only place where it is used
  • lifecycle/lifecycles shall be moved to blueprint
    • its description tells that it describes the BOM lifecycle
    • cyclonedx may inherit it from blueprints and override the description
  • ordinalVersion shall be moved to blueprint - the only place where it is used
  • origin/originRegion shall be moved to component - the only place where it is used
Lenguaje dominante
XSLT
Estrellas
567
Forks
95
Merge medio
2 d 21 h
PR fusionados (30 d)
13

Preparar el entorno

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 CycloneDX/specification

Todos los issues de CycloneDX/specification

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.