Skip to content

[Due for payment 2026-02-17] [BT-001] Add Dynamic Routes Configuration #80906

Closed

Description

@mjasikowski

Description

Current State:

  • Routes are defined as static paths in ROUTES.ts
  • Each verify-account variant requires a separate route definition
  • The VERIFY_ACCOUNT constant exists (line 52) but is just a string literal
  • No centralized configuration for dynamic route suffixes
  • Each verify-account screen has its own type definition and linking config entry

Implementation:
This task sets up all the configuration required for dynamic routes across 4 files:

  1. ROUTES.ts - Add DYNAMIC_ROUTES configuration and types
  2. SCREENS.ts - Add screen key constant
  3. types.ts - Add dynamic route param types
  4. linkingConfig/config.ts - Add dynamic route screen mapping

Part A: ROUTES.ts Configuration

File: App/src/ROUTES.ts

Add DynamicRouteConfig type definition and DYNAMIC_ROUTES configuration object:

type DynamicRouteConfig = {
    path: string;
    entryScreens: Screen[];
};

const DYNAMIC_ROUTES = {
    VERIFY_ACCOUNT: {
        path: 'verify-account',
        entryScreens: [], // Populated during migration
    },
} as const satisfies Record<string, DynamicRouteConfig>;

type DynamicRouteSuffix = (typeof DYNAMIC_ROUTES)[keyof typeof DYNAMIC_ROUTES]['path'];

Part B: SCREENS.ts Configuration

File: App/src/SCREENS.ts

Add screen key constant:

DYNAMIC: {
    VERIFY_ACCOUNT: 'Dynamic_Verify_Account',
},

Part C: Type Definitions

File: App/src/libs/Navigation/types.ts

Add dynamic route param types and exports.

Part D: Linking Config

File: App/src/libs/Navigation/linkingConfig/config.ts

Add dynamic route screen entry to the appropriate navigator.


Scope

Files:

  • App/src/ROUTES.ts
  • App/src/SCREENS.ts
  • App/src/libs/Navigation/types.ts
  • App/src/libs/Navigation/linkingConfig/config.ts

Dependencies: None (first task in sequence)

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jan 29, 2026
  2. DylanDylann commented on Feb 10, 2026

    @DylanDylann
    Contributor

    @mjasikowski Could you please assign me to this issue? I've already reviewed the PR

  3. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 10, 2026
  4. changed the title [-][BT-001] Add Dynamic Routes Configuration[/-] [+][Due for payment 2026-02-17] [BT-001] Add Dynamic Routes Configuration[/+] on Feb 10, 2026
  5. melvin-bot commented on Feb 10, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  6. melvin-bot commented on Feb 10, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.15-10 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-02-17. 🎊

    For reference, here are some details about the assignees on this issue:

  7. mjasikowski commented on Feb 11, 2026

    @mjasikowski
    ContributorAuthor

    @Expensify/bug-zero can you handle payment to @DylanDylann for the PR review please?

  8. twisterdotcom commented on Feb 11, 2026

    @twisterdotcom
    Contributor

    Payment Summary:

  9. JmillsExpensify commented on Feb 24, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @DylanDylann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionInternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions