Feat/include nomenclatures in csv parser - #432
Draft
EliNoden wants to merge 7 commits into
Draft
Conversation
EliNoden
force-pushed
the
feat/include-nomenclatures-in-csv-parser
branch
from
July 28, 2026 15:37
15f17aa to
9d80a4c
Compare
EliNoden
marked this pull request as draft
July 30, 2026 09:19
EliNoden
force-pushed
the
feat/include-nomenclatures-in-csv-parser
branch
from
July 30, 2026 13:51
96da670 to
470a1d4
Compare
|
bou3108
approved these changes
Jul 30, 2026
EliNoden
force-pushed
the
feat/include-nomenclatures-in-csv-parser
branch
7 times, most recently
from
August 14, 2026 08:14
6d5b8a5 to
173e35c
Compare
EliNoden
force-pushed
the
feat/include-nomenclatures-in-csv-parser
branch
5 times, most recently
from
August 14, 2026 12:00
3e8a2d3 to
4afd780
Compare
EliNoden
force-pushed
the
feat/include-nomenclatures-in-csv-parser
branch
from
August 14, 2026 12:10
4afd780 to
b7bc3ba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔎 Détails
Actuellement, les JSONschemas sont générés à partir des nomenclatures mais seules leurs valeurs restent sous forme d'enum.
Également, pour des nomenclatures plus permissives (code and label par exemple) on perd completement la notion de nomenclature. Pour notre travail sur le service specs, on souhaite avoir cette référence gardée dans nos schemas de sorte à ce que l'on puisse les récupérer à tout moment.
csv_parser(il manquait des flags/arguments dans le readme et le arg parser)Validation
1. générer l'avant
On va d'abord générer un
RC-EDA.old.schema.jsonpour qu'on puisse comparer les rendus.SAMU-Hub-Modeles/csv_parserLancer un csv_parser pour le RC-EDA, avec la commande :
Puis renommer le fichier généré
2. Générer l'après
Checkout sur la branche
feat/include-nomenclatures-in-csv-parser(contient les 2 commits).Relancer le parser :
3. Vérifier la différence
Observer :
🔗 Ticket associé
Asana