-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(BSR) docs(features): upgrade user's workflow #6962
base: master
Are you sure you want to change the base?
Conversation
Quality Gate passedIssues Measures |
Performance Comparison ReportSignificant Changes To Render DurationThere are no entries Meaningless Changes To Render DurationShow entries
Show details
Changes To Render CountThere are no entries Added ScenariosThere are no entries Removed ScenariosThere are no entries |
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: Diagramme des méthodes d'inscriptions | ||
--- | ||
stateDiagram-v2 | ||
direction LR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ça serait probablement plus facile à lire verticalement
direction LR | |
direction TB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
J'ai testé et je ne trouve pas, je préfère garder la version horizontale
%% style s5 fill:#BBDEFB | ||
%% style s8 fill:#00C853 | ||
%% style s12 fill:#FFCDD2 | ||
%% style s13 fill:#FFD600 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ça ne sert à rien de garder du code mort
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Je veux voir si ça colorie sur Github :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
là, c'est commenté, donc ça ne fera rien
s7:Jeunes scolarisé MEN | ||
s8:Bénéficiaire | ||
s12:Ubble | ||
s13:DMS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
il manque un lien de DMS à bénéficiaire
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep
has_subscription_pending --> beneficiary_15_17 : < 18 | ||
has_subscription_pending --> beneficiary_18 : > 18 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comment as-tu testé ?
ce lien ne se render pas bien sur GitHub https://github.com/pass-culture/pass-culture-app-native/blob/6e8f927a250753ab346f4f49be3cfca93173bfa0/doc/user_status.mmd
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
J'avais regardé le rendu pourtant et n'avais pas vu de soucis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah oui ! Je regarde ça !
@@ -34,10 +35,18 @@ stateDiagram-v2 | |||
[*] --> without_booking_18 | |||
without_booking_18 --> with_some_bookings_18 | |||
} | |||
|
|||
beneficiary_15_17 --> ex_beneficiary_15_17 : birthday 18 🎂 | |||
beneficiary_18 --> ex_beneficiary : 24 month later ⌛ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
on est précis pour les 15 17
on pourrait etre aussi précis pour les 18
beneficiary_18 --> ex_beneficiary : 24 month later ⌛ | |
beneficiary_18 --> ex_beneficiary_18 : 24 month later ⌛ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pas faux et est-ce que ce status existe car j'ai vu ça comme status pour les 15-17 ex-underage-beneficiary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
je ne sais pas
|
||
state ex_beneficiary { | ||
ex_beneficiary_18: to_old | ||
ex_beneficiary_15_17 : like_eligible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
il me semble que ce status n'éxiste pas coté backend
quand un-e bénéficiaire passe de 17 à 18 ans, iel redevient éligible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Le passage de 17 à 18 fait passer le jeu en ex_beneficiary_15_17 et il est eligible mais doit faire la procedure d'inscription 18 ans.
Comment verrais-tu la représentation ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
il est eligible mais doit faire la procedure d'inscription 18 ans.
pour moi "il est eligible" == "doit faire la procedure d'inscription 18 ans"
Le passage de 17 à 18 fait passer le jeu en ex_beneficiary_15_17
je trouve pas de status correspondant coté backend
} | ||
|
||
state ex_beneficiary { | ||
ex_beneficiary_18: to_old |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
je ne crois pas qu'il y ai de notion de "trop vieux" après les 24 mois
il me semble que c'est juste un-e ex-bénéficiaire
s7:Jeunes scolarisé MEN | ||
s8:Bénéficiaire | ||
s12:Ubble | ||
s13:DMS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
il me semble qu'on peut utiliser DMS meme si on a 15 17 et scolarisé ou si on a 18 ans et est français
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On peut aussi utiliser Ubble en étant scolarisé.
15-17 : DMS, Educonnect, Ubble.
18+ : DMS, Ubble.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Je précise MEN = Ministère de l'éduction nationale
Donc ce que je voulais représenter et qui est peut-être faux :
- 15-17 scolarisé MEN -> Educonnect
- 15-17 scolarisé non-MEN/non-scolarisé -> Ubble ou DMS mais pas Educonnect
- 18+ français à priori est routé sur Ubble et DMS si soucis mais pas DMS du premier coup
Update existing graphs and add one to explain subscription based on age and school type.
To test you can clic the "View file" menu