-
Notifications
You must be signed in to change notification settings - Fork 3
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
User Zustandification™️ #11527
User Zustandification™️ #11527
Conversation
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.
This is a ton of work! Well done.
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.
Requesting changes because: Two E2E cypress tests are failing in GitHub Actions and the same two fail for me locally.
Other notes:
I noticed we use this statement a lot when pulling in the user data to files:
useStore().user ?? {};
Is there a way we could make that logic part of the store / do we still need to optionally return the empty object? Just curious since it's used so often
Code Climate has analyzed commit f4c0cd8 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (90% is the threshold). This pull request will bring the total coverage in the repository to 95.8% (0.0% change). View more on Code Climate. |
Description
Converting the
UserContext
state management of MCR fromContext API
toZustand
(following the patterns implemented in MFP).Related ticket(s)
CMDCT-2794
How to test
Running this locally, you should be able to log in, log out, and manage Banners (as an Admin) as usual.
Optionally: install the Redux Devtools Chrome extension or the Firefox Redux Devtools extension
user
object on the extension ✨Important updates
Author checklist
convert to a different template: test → val | val → prod