Refactor subscription size page to use useSubPage hook by bernhardoj · Pull Request #80620 · Expensify/App

bernhardoj · 2026-01-27T12:41:00Z

HELD on feat: Refactor FullStep components #80354

Explanation of Change

Fixed Issues

Part of #79043
PROPOSAL:

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

NOTE: No subscription size page in Android/iOS

Go to Account > Subscription > Subscription settings > Subscription size
Enter a valid size
Press Next
Press the app go back button
Verify it goes back to the previous page
Press Next again
Press the device/browser back button
Verify it goes back to the previous page
Press Next again and Save
Verify it goes back to the Subscription settings page

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

android.mweb.mp4

iOS: Native

iOS: mWeb Safari

ios.mweb.mp4

MacOS: Chrome / Safari

web.mp4

melvin-bot · 2026-01-27T12:41:07Z

@ShridharGoel 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]

bernhardoj · 2026-01-27T12:41:53Z

@dukenv0307 @arosiclair Please check if it behaves correctly

bernhardoj · 2026-01-27T12:42:39Z

@ShridharGoel @dukenv0307 will be the reviewer here

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 835c74564a

ℹ️ 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".

src/pages/settings/Subscription/SubscriptionSize/index.tsx

codecov · 2026-01-27T12:52:08Z

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/CONST/index.ts	`87.39% <ø> (-0.11%)`	⬇️
src/ROUTES.ts	`12.89% <0.00%> (-0.15%)`	⬇️
...s/settings/Subscription/SubscriptionSize/index.tsx	`0.00% <0.00%> (ø)`
... and 66 files with indirect coverage changes

dukenv0307 · 2026-01-28T04:51:37Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- 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)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
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 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.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

Screen.Recording.2026-01-28.at.11.48.42.mov

iOS: HybridApp

iOS: mWeb Safari

Screen.Recording.2026-01-28.at.11.47.57.mov

MacOS: Chrome / Safari

Screen.Recording.2026-01-28.at.11.36.58.mov

bernhardoj · 2026-01-28T04:55:49Z

I just refactor back the const structure

dukenv0307 · 2026-01-28T09:40:53Z

I just refactor back the const structure

Great! I'm reviewing your PR and also intend to comment on this PR about it

dukenv0307 · 2026-01-28T15:00:27Z

Let's wait for this PR to be merged first

JmillsExpensify

Ultimately improving the product experience.

arosiclair

LGTM. @dukenv0307 the other PR was merged. Do you want to retest?

dukenv0307 · 2026-02-03T01:50:50Z

@arosiclair Sure, I'm on it now

dukenv0307 · 2026-02-03T02:00:03Z

Looks good

Screen.Recording.2026-02-03.at.08.59.03.mov

dukenv0307 · 2026-02-03T02:00:53Z

@bernhardoj can you please take a look at the failing test?

…ubpage

bernhardoj · 2026-02-03T09:48:20Z

@dukenv0307 just merged with main

arosiclair

LGTM, but let's wait for #80354 to deploy to prod first.

dukenv0307 · 2026-02-10T03:14:19Z

@arosiclair We're good to go

github-actions · 2026-02-10T14:46:36Z

🚧 @arosiclair has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-02-10T14:50:25Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80620.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-abff5eb-27c4bed4e1bad1547533f64eeead688916046d3b/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-abff5eb-d61873b20eca4b461028c5927fe580bab8fc178b/index.html

Web 🕸️
https://80620.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-10T14:52:16Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-02-11T06:53:31Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.3.17-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2026-02-12T15:22:50Z

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.17-9 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	failure ❌

refactor subscription size page to use useSubPage hook

835c745

bernhardoj requested review from a team as code owners January 27, 2026 12:41

melvin-bot bot assigned bernhardoj Jan 27, 2026

melvin-bot bot requested review from JmillsExpensify and ShridharGoel and removed request for a team January 27, 2026 12:41

melvin-bot bot removed the request for review from a team January 27, 2026 12:41

chatgpt-codex-connector bot reviewed Jan 27, 2026

View reviewed changes

src/pages/settings/Subscription/SubscriptionSize/index.tsx Outdated Show resolved Hide resolved

make the canChangeSize optional

a34677c

dukenv0307 approved these changes Jan 28, 2026

View reviewed changes

melvin-bot bot requested a review from arosiclair January 28, 2026 04:51

refactor back the const

e803e3d

use the correct constant

992d71e

JmillsExpensify previously approved these changes Feb 2, 2026

View reviewed changes

arosiclair reviewed Feb 2, 2026

View reviewed changes

dukenv0307 approved these changes Feb 3, 2026

View reviewed changes

melvin-bot bot requested a review from arosiclair February 3, 2026 02:00

Merge branch 'main' into chore/refactor-subscription-size-to-use-uses…

38a8351

…ubpage

show loading indicator when redirecting

8745d69

bernhardoj dismissed JmillsExpensify’s stale review via 8745d69 February 3, 2026 09:47

arosiclair previously approved these changes Feb 3, 2026

View reviewed changes

arosiclair changed the title ~~Refactor subscription size page to use useSubPage hook~~ [HOLD #80354]Refactor subscription size page to use useSubPage hook Feb 3, 2026

update route type

5236203

bernhardoj dismissed arosiclair’s stale review via 5236203 February 3, 2026 17:14

This was referenced Feb 4, 2026

Refactor add personal bank account to use useSubPage #81333

Merged

Refactor netsuite connection page to use useSubPage #80711

Merged

arosiclair changed the title ~~[HOLD #80354]Refactor subscription size page to use useSubPage hook~~ Refactor subscription size page to use useSubPage hook Feb 9, 2026

dukenv0307 approved these changes Feb 10, 2026

View reviewed changes

melvin-bot bot requested a review from arosiclair February 10, 2026 03:14

arosiclair approved these changes Feb 10, 2026

View reviewed changes

arosiclair merged commit abff5eb into Expensify:main Feb 10, 2026
33 checks passed

OSBotify mentioned this pull request Feb 11, 2026

Deploy Checklist: New Expensify 2026-02-11 #82079

Closed

jponikarchuk mentioned this pull request Feb 11, 2026

Subscription - Semi transparent loading page appears when opening Subscription size page #82096

Closed

7 tasks

This was referenced Feb 11, 2026

Revert "Refactor subscription size page to use useSubPage hook" #82136

Merged

[CBN] Refactor subscription size flow #79043

Closed

Conversation

bernhardoj commented Jan 27, 2026 • edited by arosiclair Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 27, 2026

Uh oh!

bernhardoj commented Jan 27, 2026

Uh oh!

bernhardoj commented Jan 27, 2026

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

codecov bot commented Jan 27, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

dukenv0307 commented Jan 28, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

bernhardoj commented Jan 28, 2026

Uh oh!

dukenv0307 commented Jan 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dukenv0307 commented Jan 28, 2026

Uh oh!

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

arosiclair left a comment

Choose a reason for hiding this comment

Uh oh!

dukenv0307 commented Feb 3, 2026

Uh oh!

dukenv0307 commented Feb 3, 2026

Uh oh!

dukenv0307 commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bernhardoj commented Feb 3, 2026

Uh oh!

arosiclair left a comment

Choose a reason for hiding this comment

Uh oh!

dukenv0307 commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Feb 10, 2026

Uh oh!

github-actions bot commented Feb 10, 2026

Uh oh!

OSBotify commented Feb 10, 2026

Uh oh!

OSBotify commented Feb 11, 2026

Uh oh!

OSBotify commented Feb 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

bernhardoj commented Jan 27, 2026 •

edited by arosiclair

Loading

codecov bot commented Jan 27, 2026 •

edited by github-actions bot

Loading

dukenv0307 commented Jan 28, 2026 •

edited

Loading

dukenv0307 commented Feb 3, 2026 •

edited

Loading

dukenv0307 commented Feb 10, 2026 •

edited

Loading