feat/US222-new-resin-repository
 |
|---|
What does this MR do and why?
Describe in detail what your merge request does and why.
 |
|---|
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally (or on alpha)
You will need to test the following on this MR :
-
Onboarding -
Structure create -
Structure update -
User personal offer for a structure
-
-
Carto -
Search filters -
Structure detail panel -
Structure print
-
-
Profil -
Structure display
-
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.
Merge request reports
Activity
requested review from @ELOUPIAS
assigned to @ext.sopra.husubtil
changed milestone to %[Res'in] 2.0
Resolved by Etienne LOUPIASIl me semble qu'il manque par rapport à la maquette le label "Publics accueillis" au-dessus de "Familles et/ou enfants"
Edited by Etienne LOUPIAS- Last reply by Hugo SUBTIL
- Resolved by Hugo SUBTIL
Sur l'onboarding, c'est pas un vrai retour mais plus la question dont on a déjà parlé tout à l'heure : ça parait bizarre d'avoir "Uniquement femmes" en premier, sans titre, sans savoir si c'est obligatoire ou facultatif, puis d'être obligé de choisir un âge et de tout cocher si on est tout public
- Last reply by Hugo SUBTIL
- Resolved by Hugo SUBTIL
D'après la maquette il manque l'écran pour saisir le champ libre si on choisit "Autres" dans les démarches en ligne (mais le pb date d'avant l'US)
- Last reply by Hugo SUBTIL
- Resolved by Etienne LOUPIAS
Sur cet écran des autres services, si on coche la 1ère case "Vente de matériel numérique à tarif solidaire", qu'on fait Suivant, puis Précédent, la 1ère cas n'est plus cochée (le pb se pose que sur la 1ère case)
- Last reply by Hugo SUBTIL
- Resolved by Etienne LOUPIAS
Sur le même écran ci-dessus, il y a des différences avec la maquette : https://www.figma.com/file/sTEFbJiag3Klhvx9eO1pvW/R%C3%A9s%27in-%5BRecherches%5D?node-id=5970%3A71016
notamment le texte "(Ordinateur, smartphone, clé 4G, forfait internet…)" qui manque, et la largeur des cases qui est petite
Edited by Etienne LOUPIAS - Last reply by Hugo SUBTIL
- Resolved by Hugo SUBTIL
Dans le profil, puis modifier la structure, les libellés sont les anciens :
