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
This issue has not been updated in over 15 days. @mjasikowski, @suneox, @huult eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Started with 3 onboarding routes, but all three are blocked from migration. ONBOARDING_PERSONAL_DETAILS, ONBOARDING_PRIVATE_DOMAIN, and ONBOARDING_EMPLOYEES are fixed sibling steps in the onboarding wizard, with state-driven navigation and backTo carried across the flow, so their back destinations cannot be derived from the URL. Therefore, they don't fit the current dynamic-route mechanism and would require a separate onboarding navigation refactor.
@collectioneur Could you advise on this? Can we skip migrating these routes?
Yes, I’ve looked into it a couple of days ago, and I agree that we need a different strategy here, since these routes are built a little differently and don’t quite fit the dynamic routes use case
Activity
36 remaining items
melvin-bot commentedon Jul 27, 2026
This issue has not been updated in over 15 days. @mjasikowski, @suneox, @huult eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
huult commentedon Jul 29, 2026
Only 3 routes that use backTo need to be migrated: ONBOARDING_PERSONAL_DETAILS, ONBOARDING_PRIVATE_DOMAIN, and ONBOARDING_EMPLOYEES.
huult commentedon Aug 14, 2026
Started with 3 onboarding routes, but all three are blocked from migration. ONBOARDING_PERSONAL_DETAILS, ONBOARDING_PRIVATE_DOMAIN, and ONBOARDING_EMPLOYEES are fixed sibling steps in the onboarding wizard, with state-driven navigation and backTo carried across the flow, so their back destinations cannot be derived from the URL. Therefore, they don't fit the current dynamic-route mechanism and would require a separate onboarding navigation refactor.
@collectioneur Could you advise on this? Can we skip migrating these routes?
collectioneur commentedon Aug 14, 2026
Yes, I’ve looked into it a couple of days ago, and I agree that we need a different strategy here, since these routes are built a little differently and don’t quite fit the dynamic routes use case
huult commentedon Aug 14, 2026
@mjasikowski Per this comment, I think we can close this ticket since there's nothing we need to do here.