-
Notifications
You must be signed in to change notification settings - Fork 6
ActiveModal refactor #1809
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
ActiveModal refactor #1809
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1809 +/- ##
==========================================
+ Coverage 41.56% 41.64% +0.08%
==========================================
Files 543 543
Lines 23784 23844 +60
Branches 7863 7929 +66
==========================================
+ Hits 9885 9931 +46
- Misses 13256 13267 +11
- Partials 643 646 +3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
[VRT] Update baselines for active-modal-refactor
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.
It's nice to have some tidier logic here, and the teacher onboarding modal looks great with the animations.
The only issue I've found is with non-paginated modals: it seems to be counting each character in the body as its own page, which yields some interesting modals:
Otherwise this all looks good 👍
|
Ah, strings are structurally very similar to arrays so a modal with a |
[VRT] Update baselines for active-modal-refactor
(Please see #1660 for prior context)
This takes on many of the suggestions implemented by the PR above, but does away with the separation between stateful and non-stateful modals. Since we now rely exclusively on the ID in Redux to store which modal(s) are open, we are free to fill the contents of the modals with state if they so require, though in truth I do not believe they should ever need any given they exist as sources of information, not interactivity.
I have moved the pagination logic to inside ActiveModal, as I believe this is going to become a very common use case given various discussions. To allow this, what is passed to
bodynow determines whether pagination occurs; if this is a list of items, each item is interpreted as its own page in the modal, and a "Next" button is used to go from one to the next (TODO: "Previous"?). This also means the same logic / animation will be used to travel between the pages, when this gets built.