Report an expansion whose locked repo version was deleted
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
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Área
- backend
Línea de trabajo
Start by reading the linked epic OpenConceptLab/ocl_issues#2942 and dependency #3003 to find the affected repository and how expansion health reasons and rebuild offers are handled. Then trace repo version deletion and its unit tests for source and collection versions. Done means deletion records the version on each locked expansion, members stay unchanged, and both version cases are covered by tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Repo: oclapi2 · Depends on: OpenConceptLab/ocl_issues#3003
Part of OpenConceptLab/ocl_issues#2942, the epic's open edge case. Deleting a repo version removes the lock from the expansion, so a later add falls back to the latest release with no sign of it, and this can't be detected afterwards. It has to be recorded at delete time.
Decided (Jon, Nov 3): a health reason, not an unresolved_repo_versions entry, so FHIR $expand keeps answering.
ACs
- Deleting a repo version records, on each expansion locked to it, which version was deleted.
- OpenConceptLab/ocl_issues#3003 reports it as a reason, and the expansion's owner is offered a rebuild.
- Members don't change.
- Unit tests for a source version and a collection version.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 4
- Forks
- 2
- Merge medio
- 2 h 12 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de OpenConceptLab/ocl_issues
-
component/fhir type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
OpenConceptLab/ocl_issues#3026 ·
-
component/api decision/human-review signal/needs-access signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
OpenConceptLab/ocl_issues#3012 · 2 comentarios ·
-
component/design-system decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/docs
Dificultad 2/5 Medio día Aptitud para principiantes 70/100
OpenConceptLab/ocl_issues#2983 · 1 comentario ·
-
component/mapper decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
OpenConceptLab/ocl_issues#2966 · 2 comentarios ·
-
component/mapper component/web decision/human-review signal/low-risk signal/needs-human signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
OpenConceptLab/ocl_issues#2920 · 1 comentario ·
Todos los issues de OpenConceptLab/ocl_issues
Issues similares
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
coder/claudecode.nvim#587 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
digitalbazaar/http-client#60 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
fivetran/dbt_recurly#55 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
topmonks/hlidac-shopu#3687 ·
Los mantenedores suelen responder en 1 día
-
bug lane: fast
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
unicef/adt-studio#1109 ·
Los mantenedores suelen responder en 2 días