Repository navigation
Closed
Labels
InternalRequires API changes or must be handled by Expensify staffRequires API changes or must be handled by Expensify staffMonthlyKSv2KSv2Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.Skips all the payment process steps for an issue. Use it for fixed-price projects.
Description
Description
Current State:
- 5 routes for onboarding features and work email
- These routes use
backToparameter for return navigation
Implementation:
- Replace
getRoute(..., backTo)withcreateDynamicRoute() - Add source screens to
entryScreensarray - Remove
backToparameter from route definitions - Test forward/back navigation
Scope
Routes (5):
| Route Constant | Path |
|---|---|
ONBOARDING_INTERESTED_FEATURES |
onboarding/interested-features |
ONBOARDING_PURPOSE |
onboarding/purpose |
ONBOARDING_WORKSPACES |
onboarding/join-workspaces |
ONBOARDING_WORK_EMAIL |
onboarding/work-email |
ONBOARDING_WORK_EMAIL_VALIDATION |
onboarding/work-email-validation |
Usages
ONBOARDING_INTERESTED_FEATURES:
- Search for usages in features selection flow
ONBOARDING_PURPOSE:
- Search for usages in purpose selection flow
ONBOARDING_WORKSPACES:
- Search for usages in workspaces join flow
ONBOARDING_WORK_EMAIL:
- Search for usages in work email flow
ONBOARDING_WORK_EMAIL_VALIDATION:
- Search for usages in work email validation flow
Files to modify:
src/ROUTES.ts- Update route definitionssrc/libs/Navigation/types.ts- RemovebackTofrom params- Components listed above
Migration Progress
-
ONBOARDING_INTERESTED_FEATURES -
ONBOARDING_PURPOSE -
ONBOARDING_WORKSPACES -
ONBOARDING_WORK_EMAIL -
ONBOARDING_WORK_EMAIL_VALIDATION
Issue Owner
Current Issue Owner: @suneoxMetadata
Metadata
Assignees
Labels
InternalRequires API changes or must be handled by Expensify staffRequires API changes or must be handled by Expensify staffMonthlyKSv2KSv2Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.Skips all the payment process steps for an issue. Use it for fixed-price projects.
Activity
5 remaining items
melvin-bot commentedon Jun 8, 2026
This issue has not been updated in over 15 days. @mananjadhav, @mjasikowski, @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 two routes that use backTo need to be migrated: ONBOARDING_PURPOSE and ONBOARDING_WORKSPACES.
huult commentedon Aug 14, 2026
ONBOARDING_WORKSPACES and ONBOARDING_PURPOSE don't fit the dynamic-route mechanism because they are fixed onboarding wizard steps with state-driven navigation, backTo passed through the flow, and custom forceReplace/refresh handling. I recommend skipping the remaining ONBOARDING_* routes and treating onboarding navigation as a separate refactor.
huult commentedon Aug 14, 2026
@mjasikowski Per #83870 (comment), I think we can close this ticket since there's nothing we need to do here.