Skip to content

Plan selector modal migration#96745

Open
jmusial wants to merge 2 commits into
Expensify:mainfrom
software-mansion-labs:chore/migrate-workspace-plan-selector-modal-to-navigation
Open

Plan selector modal migration#96745
jmusial wants to merge 2 commits into
Expensify:mainfrom
software-mansion-labs:chore/migrate-workspace-plan-selector-modal-to-navigation

Conversation

@jmusial

@jmusial jmusial commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Migrates the workspace plan type selector in the workspace confirmation flow from an inline popover component (PlanTypeSelector) to a dedicated navigation page (DynamicWorkspacePlanTypeSelectionPage) registered as a dynamic route in the RHP.

The selection is now persisted via the form draft in Onyx, and the shared default-plan logic was extracted to getDefaultWorkspacePlanType in PolicyUtils.

Fixed Issues

$ #96756
PROPOSAL:

Tests

Pre requisite:
User needs to be an approved accountant or to test locally w/o this paste following snippet in console:

Onyx.merge('account', {isApprovedAccountant: true});

This will result in workspace creation failing though.

  1. Open app.
  2. Navigate to Workspaces
  3. Press + New
  4. Verify that Plan input is visible
  5. Verify that once pressed it opens selection RHP
  6. Verify that you can select plan using it

Offline tests

Same as tests.

QA Steps

Same as tests.

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Screen.Recording.2026-07-23.at.15.06.41.mov
Android: mWeb Chrome
Screen.Recording.2026-07-23.at.15.07.46.mov
iOS: Native
Screen.Recording.2026-07-23.at.15.01.27.mov
iOS: mWeb Safari
Screen.Recording.2026-07-23.at.15.03.08.mov
MacOS: Chrome / Safari
Screen.Recording.2026-07-23.at.14.49.33.mov

@mountiny

Copy link
Copy Markdown
Contributor

Linked sub-issue for this migration: #96756

@codecov

codecov Bot commented Jul 23, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/ROUTES.ts 21.55% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 66.66% <ø> (ø)
src/types/form/WorkspaceConfirmationForm.tsx 0.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 6.49% <0.00%> (-0.01%) ⬇️
src/components/WorkspaceConfirmationForm.tsx 0.00% <0.00%> (ø)
src/libs/PolicyUtils.ts 76.86% <0.00%> (-0.20%) ⬇️
...orkspace/DynamicWorkspacePlanTypeSelectionPage.tsx 0.00% <0.00%> (ø)
... and 14 files with indirect coverage changes

@jmusial

jmusial commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 820ed95261

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@jmusial
jmusial marked this pull request as ready for review July 23, 2026 13:09
@jmusial
jmusial requested review from a team as code owners July 23, 2026 13:09
@melvin-bot
melvin-bot Bot requested a review from dmkt9 July 23, 2026 13:09
@melvin-bot

melvin-bot Bot commented Jul 23, 2026

Copy link
Copy Markdown

@dmkt9 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot requested review from heyjennahay and removed request for a team July 23, 2026 13:09

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 820ed95261

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/ROUTES.ts
Comment on lines +143 to +145
WORKSPACE_CONFIRMATION_PLAN_TYPE: {
path: 'plan-type',
entryScreens: [SCREENS.WORKSPACE_CONFIRMATION.DYNAMIC_ROOT],

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Allow plan selector from all shared form hosts

When an approved accountant opens this shared WorkspaceConfirmationForm from the travel workspace confirmation or the IOU upgrade flow, the plan row now calls createDynamicRoute(...plan-type) from SCREENS.TRAVEL.WORKSPACE_CONFIRMATION or SCREENS.MONEY_REQUEST.STEP_UPGRADE; getStateFromPath validates dynamic routes against entryScreens, so limiting this suffix to only SCREENS.WORKSPACE_CONFIRMATION.DYNAMIC_ROOT rejects those URLs and the selector won't open in those existing flows. Include the other screens that render the form, or keep this selector local for non-workspace-confirmation hosts.

Useful? React with 👍 / 👎.

const backPath = useDynamicBackPath(DYNAMIC_ROUTES.WORKSPACE_CONFIRMATION_PLAN_TYPE.path);

const [workspaceConfirmationFormDraft] = useOnyx(ONYXKEYS.FORMS.WORKSPACE_CONFIRMATION_FORM_DRAFT);
const [policies] = useOnyx(ONYXKEYS.COLLECTION.POLICY);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-11 (docs)

This subscribes to the entire ONYXKEYS.COLLECTION.POLICY collection without a selector, but the only use of policies is to derive a single scalar (getDefaultWorkspacePlanType(policies) returns a PolicyType). Without a selector Onyx will re-render this page whenever any field of any policy changes, even though the page only cares about whether the user belongs to a Control workspace.

Use a selector that reduces the collection to the primitive the page actually needs, so deepEqual runs on a tiny value and unrelated policy updates don't trigger re-renders:

const [defaultPlanType] = useOnyx(ONYXKEYS.COLLECTION.POLICY, {
    selector: (policies) =>
        Object.values(policies ?? {}).some((policy) => policy?.type === CONST.POLICY.TYPE.CORPORATE)
            ? CONST.POLICY.TYPE.CORPORATE
            : CONST.POLICY.TYPE.TEAM,
});

const planType = workspaceConfirmationFormDraft?.planType ?? defaultPlanType;

Reviewed at: 820ed95 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

isSelected: policyType === planType,
}));

const handleSelect = (option: PlanTypeItem) => {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-12 (docs)

The handler handleSelect is named for the event slot it is wired to (onSelectRow) rather than for the action it performs. It saves the chosen plan type as a draft value and navigates back — its name should describe that behavior. The on*/handle* prefix belongs on the JSX prop, not the function definition.

const savePlanType = (option: PlanTypeItem) => {
    setDraftValues(ONYXKEYS.FORMS.WORKSPACE_CONFIRMATION_FORM, {[INPUT_IDS.PLAN_TYPE]: option.value});
    Navigation.goBack(backPath, {shouldSkipFocusRestore: true});
};

// ...
<SelectionList onSelectRow={savePlanType} ... />

Reviewed at: 820ed95 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

// uses to keep the initially selected row in sync with what the form shows.
const planType = workspaceConfirmationFormDraft?.planType ?? getDefaultWorkspacePlanType(policies);

const handleBackPress = () => {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ CONSISTENCY-12 (docs)

The handler handleBackPress is named for the triggering event (back press) rather than the action it performs (navigating back). Name it for the behavior and keep the on* prefix on the JSX prop only.

const goBack = () => {
    Navigation.goBack(backPath);
};

// ...
<HeaderWithBackButton title={translate('workspace.common.planType')} onBackButtonPress={goBack} />

Reviewed at: 820ed95 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants