-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove page-based modals in favor of existing state-based modal logic #1270
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
a415ab5
to
5578f18
Compare
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger
Smaller
Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
4230169
to
2b03108
Compare
Can you explain this a bit more? I think I'm missing some context so I don't understand why this change is necessary and what problem it would solve. |
Right now, we have two parallel systems for displaying modals on top of the current page. One of them uses an array of modals stored in Redux state, then manually renders those modals in an overlay. The other one uses a linked list of modals stored as the current location, with the While the location-based modals offer some advantages (for example, they update the URL when invoked, and we can use React Router's matching logic to select which modals to display, it requires a few hacks:
|
Thanks for the explanation. Yes, it makes sense to port everything over to a single system. Thanks for taking this up! I'll do a review once all the CI jobs pass. |
Fixed the CI! |
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.
Would appreciate a review from @trevdor too since he's our react-router expert.
packages/desktop-client/src/components/schedules/LinkSchedule.js
Outdated
Show resolved
Hide resolved
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.
LGTM on my end
🦥 I'm slow to get to this, but aim to look at it later tonight. |
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.
SO much easier to reason about when all modals follow a single paradigm. Thank you!
…actualbudget#1270) Co-authored-by: Trevor Farlow <[email protected]>
Fixes #1264