Repository navigation
Closed
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to productionInternalRequires API changes or must be handled by Expensify staffRequires API changes or must be handled by Expensify staffWeeklyKSv2KSv2
Description
Description
Current State:
- The current dynamic route implementation only supports a single suffix level (e.g.,
/base-path/verify-account) - Nested routes like
settings/profile/address/countryrequire multiple suffix layers (e.g.,/profile+/address/country) - This limitation was discovered during BT-102 migration work
Expected State:
- Support suffix layering so dynamic routes can be nested (e.g.,
/settings/profile/address/countrybuilt from/settings+/profile+/address/country) - The
createDynamicRoute()helper andgetAdaptedStateFromPathinterception logic must handle multiple dynamic suffix levels - Access control (
entryScreens) should validate at each layer - Back navigation should correctly strip one suffix layer at a time
Implementation:
- Extend
createDynamicRoute()to support appending suffixes onto paths that already contain dynamic suffixes - Update suffix detection in
getMatchingFullScreenRoute()to recursively or iteratively resolve layered suffixes - Ensure state restoration (page refresh / deep link) correctly rebuilds the full nested navigation state
- Update unit tests to cover layered suffix scenarios
Context
See discussion: #83361 (comment)
This is a blocker for migrating routes with nested dynamic suffixes across Phase 2.
Scope
Files:
App/src/libs/Navigation/Navigation.ts- ExtendcreateDynamicRoute()for layered suffixesApp/src/libs/Navigation/helpers/getAdaptedStateFromPath.ts- Handle layered suffix resolutionApp/src/ROUTES.ts- May needDYNAMIC_ROUTESconfig updates for nested paths- Test files for dynamic routing
Dependencies:
- [Due for payment 2026-02-17] [BT-001] Add Dynamic Routes Configuration #80906
- [Due for Payment meow][BT-002] Implement createDynamicRoute() Helper #80907
- [BT-003] Intercept and Validate Dynamic Suffixes #80908
Issue Owner
Current Issue Owner: @collectioneurMetadata
Metadata
Assignees
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionAuto-added when associated PR is deployed to productionInternalRequires API changes or must be handled by Expensify staffRequires API changes or must be handled by Expensify staffWeeklyKSv2KSv2
Activity
mjasikowski commentedon Feb 26, 2026
@collectioneur will handle the PR here
[-][BT-008] Implement Dynamic Suffix Layering[/-][+][Due for payment 2026-03-16] [BT-008] Implement Dynamic Suffix Layering[/+]melvin-bot commentedon Mar 9, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".12 remaining items
[-][BT-008] Implement Dynamic Suffix Layering[/-][+][Due for payment 2026-03-30] [BT-008] Implement Dynamic Suffix Layering[/+]melvin-bot commentedon Mar 23, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-30. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 23, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)[-][Due for payment 2026-03-30] [BT-008] Implement Dynamic Suffix Layering[/-][+][BT-008] Implement Dynamic Suffix Layering[/+]mallenexpensify commentedon Mar 30, 2026
If payment is due for @huult please tag me and make me issue own. (and reopen) thx
huult commentedon Mar 31, 2026
@mallenexpensify FYI: #83551 (comment)