You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current researching how to do global modals (available on any url) and have seen other discussions that suggest using a search param (eg /?modal=login)
Wanting to take that idea a step further and essentially have an entire modal routing system so I can do things like "/?modal=/job/:id/status".
Which then begs the question of nested route elements - eg split 'job', ':id' and 'status' giving each an element with an outlet.
I feel like the best way to do that would be with a second router which derives its location from the search (rather than using search matching itself).
Has anyone tried doing something partiuclarly advanced with global modal routing?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Current researching how to do global modals (available on any url) and have seen other discussions that suggest using a search param (eg /?modal=login)
Wanting to take that idea a step further and essentially have an entire modal routing system so I can do things like "/?modal=/job/:id/status".
Which then begs the question of nested route elements - eg split 'job', ':id' and 'status' giving each an element with an outlet.
I feel like the best way to do that would be with a second router which derives its location from the search (rather than using search matching itself).
Has anyone tried doing something partiuclarly advanced with global modal routing?
Beta Was this translation helpful? Give feedback.
All reactions