-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feat/init paradata #154
Feat/init paradata #154
Conversation
69762b7
to
8bc83ad
Compare
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.
Great, but I've make some comments.
9e1b963
to
ce629fa
Compare
} | ||
} | ||
triggerDataAndStateUpdate() |
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.
Ici on va trigger l'update sans condition (là où avant on vérifiait qu'il y avait de la donnée modifiée), ça me paraît pas problématique mais à avoir en tête
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.
Oui garder la logique qu'on avait avant serait mieux ^^
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.
finalement c'était le seul cas qui vérifiait, le logout trigger sans condition (alors que comme ici on n'a potentiellement rien à modifier car on reste sur la même page) => pas très cohérent
Le seul cas qui ne nécessite pas de vérification est le changement de page (on veut a minima update le currentPage), pour les autres est-ce nécessaire... ?
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.
Petite question, il y a un réel gain à faire 2 useEffect au lieu d'un seul ? (j'ai pas la réponse)
} | ||
} | ||
triggerDataAndStateUpdate() |
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.
Oui garder la logique qu'on avait avant serait mieux ^^
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.
Review en diagonale (la PR est un peu longue 🥵 )
Sur le truc de la constante à gauche dans les comparaisons, je l'ai pas relevé partout, me semble que c'est une bonne pratique à introduire dans les nouveaux devs (sous réserve que vous trouviez ça pertinent), mais pas matière à refacto toute l'appli en ce sens imo
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.
👍 👍
dbd45a9
to
c3a0f51
Compare
c3a0f51
to
b1b1184
Compare
Quality Gate passedIssues Measures |
No description provided.