Split User into Account and PasswordUser #364
Merged
Conversation
This file contains 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
florimondmanca
added
refactor
florimondmanca
force-pushed
the
fm/account-password-user
branch
4 times, most recently
from
e7b6068 to
1f801ec
Compare
11 tasks
florimondmanca
force-pushed
the
fm/account-password-user
branch
from
1f801ec to
c0746ee
Compare
florimondmanca
force-pushed
the
fm/account-password-user
branch
from
c0746ee to
1c50215
Compare
Validation staging
|
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.
Closes #362
Cette PR décompose l'entité existante
Useren deux entités:Account: contient les données "génériques" liées aux comptes utilisateurs dans l'outilPasswordUser: contient les données "spécifiques" à une authentification par couple email/mdp, en l'occurrence seulement lepassword_hashLa convention est :
password_user(données "spécifiques") (et bientôt desdatapass_user, refs Intégration backend avec Comptes DataPass #361) via les commandsaccounts(données "génériques") via les queriesDe cette façon la présentation reste unifiée via l'interface
AccountView.De fait, il n'y a aucune incidence du point de vue du frontend, qui manipulait déjà des
UserView, renommées enAccountView. (Faut-il renommer les entités côté frontend enAccount? Pour l'instant elles restent desUser.)TODO