[Bug]: Term row duplication when generating page for 3 versions with a recent type change
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
The issue points to the Makefile and the script that compares version CSVs, but does not name the script or its tests. Start by reading the Makefile entries for the release CSVs and the comparison script; the reported result is one citation row per version without duplicate rows. The issue says this will be fixed by #132, so check that work before starting.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Is this the right place?
- This is NOT an addition, alteration or removal of CodeMeta terms. Please raise terms issues in the main CodeMeta repository.
- This is NOT about the CodeMeta Generator. Please raise Generator issues in the Codemeta-Generator repository.
Which pages are affected?
When for QA purposes the Makefile is amended to include the current prospective release branch's CSV, the citation row appears 3 times, and last two of them are identical except for the version number
The reason for this is that the script was made for 2 current releases, so both v3 and v2 are compared to v4. Since v4 changes citation's type, a new row is added after checking the older versions against it, for both of them. Had this been a description.
Had the change been description, it would have been handled as expected, as this is what the previous script alteration was working around.
This will be fixed by #132
Which browsers are you seeing the problem on?
No response
Any other information?
- Lenguaje dominante
- CSS
- Estrellas
- 5
- Forks
- 23
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una 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 codemeta/codemeta.github.io
-
content
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
codemeta/codemeta.github.io#141 ·
-
[tools page] CFFR is not listedAbiertocontent
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
codemeta/codemeta.github.io#138 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
codemeta/codemeta.github.io#129 · 5 comentarios ·
-
content
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
codemeta/codemeta.github.io#123 · 1 comentario ·
-
content
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
codemeta/codemeta.github.io#121 ·
Todos los issues de codemeta/codemeta.github.io
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
5hyuns/maya-workflow-kit-for-blender#338 ·
Los mantenedores suelen responder en 1 día
-
`isCI` is `true` inside a running Google Cloud Run service (also Railway, Render, Deno Deploy)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
btclib-org/claude-process#341 ·
-
area: settings follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
manaflow-ai/cmux#37992 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
dependents/node-precinct#167 ·