[GH-ISSUE #1264] Migrate all URL-based modals (usePushModal) to the state-based system (dispatch(pushModal(...))) #7413

Closed
opened 2026-04-10 17:14:17 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @j-f1 on GitHub (Jul 2, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1264

Many modals currently use the dispatch(pushModal()) / actions.pushModal system instead of the (presumably?) newer router-based usePushModal system. When touching these modals, we should migrate them to the new system.

Originally created by @j-f1 on GitHub (Jul 2, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1264 Many modals currently use the `dispatch(pushModal())` / `actions.pushModal` system instead of the (presumably?) newer router-based `usePushModal` system. When touching these modals, we should migrate them to the new system.
GiteaMirror added the tech debt label 2026-04-10 17:14:17 -05:00
Author
Owner

@j-f1 commented on GitHub (Jul 3, 2023):

Thinking about this again, I think we should go the other way — usePushModal modals are weird because they affect the URL which messes up a bunch of subtle things in the app (including the way they take up the whole page if you refresh while one is open).

<!-- gh-comment-id:1617017448 --> @j-f1 commented on GitHub (Jul 3, 2023): Thinking about this again, I think we should go the other way — `usePushModal` modals are weird because they affect the URL which messes up a bunch of subtle things in the app (including the way they take up the whole page if you refresh while one is open).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#7413