Resolve "[DATA] - Finaliser l'intégration dans la plateforme data.grandlyon.com uniquement"
requested to merge 26-data-finaliser-l-integration-dans-la-plateforme-data-grandlyon-com-uniquement into dev
Related to #26 (closed)
What does this MR do and why?
Cette MR permet d'exposer les données des structures res'in au format de l'état (mednum) sur l'endpoint /api/structures/formated
How to set up and validate locally (or on alpha)
Avoir des structures en base avec le partage vers data.grandlyon activé (champ dataShareConsentDate)
Se rendre sur localhost:4200/api/structures/formated
Vérifier que chaque objet contient à minima les propriétés obligatoires du schéma de l'état :
https://lamednum.coop/schema-de-donnees-des-lieux-de-mediation-numerique-2/
PS. Le champ "antenne" bien qu'obligatoire n'est pas renvoyé actuellement car la donnée n'est pas traité dans res'in pour le moment.
MR acceptance checklist
To be completed by the chosen reviewer.
Quality 
-
- For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users. If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR.
- I have made sure that the sonar quality coverage is up to standards.
- I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
- I have tested this MR in all supported browsers or determined that this testing is not needed.
- I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.
Performance, reliability and availability
- I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
- I have considered the scalability risk based on future predicted growth.
Documentation
- The MR is named after the desired squash commit to feed the changelog linked to the current milestone.
- I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.
Security
- I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.
Deployment
- When featured on a self-data project release, I have made sure my app version in the manifest and package.json is incremented and any relative changes to the permissions are clearly written and transmitted to Cozy.
Related to #26 (closed)
Edited by Hugo NOUTS