Mapper: Context is saved but the API never returns it, so the next save erases it
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- django, javascript, python
Línea de trabajo
Start in core/map_projects/serializers.py and trace MapProjectSerializer, MapProjectDetailSerializer and the create/update serializer; then inspect MapProject.jsx to follow how Context is loaded and saved. Check whether Create similar copies configurations, including the configurations/ path named in the issue. Add coverage for saving Context, reading it after reload and saving again; done when the API returns the saved description and the round trip preserves it.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Found on production (API 2.3.227, Mapper 1.0.31-beta) on 2026-10-20 while preparing the OHDSI 2026 Mapper demo.
The Mapper's Context field (Configure) is stored in MapProject.description. MapProjectCreateUpdateSerializer accepts it, but no read serializer returns it:
core/map_projects/serializers.py:MapProjectSerializer.Meta.fields, and soMapProjectDetailSerializer, leave outdescription.MapProject.CONFIGURATION_FIELDSdoesn't include it either.- oclmap loads it with
setDescription(response.data?.description || '')(MapProject.jsx), so it always loads'', and every save sendsdescriptionback (formData.append('description', description)).
Reproduced on a project:
- Enter Context and save. The
map_projectsrow has the text. - Reload the project. Context is blank.
- Save again for any reason.
descriptionis now''in the database.
Every user who fills in Context loses it on the next save after a reload, with no warning.
Acceptance criteria
-
GETon a map project returnsdescription. - After a reload the Mapper shows the saved Context, and saving keeps it.
- Decide whether Create similar copies Context; if so, include it in
configurations/. - A test covers the save, read and save-again round trip.
- 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