Skip to content

Strip new magic codes instances - #97457

Open
NikkiWines wants to merge 7 commits into
mainfrom
nikki-magic-code-followup
Open

Strip new magic codes instances#97457
NikkiWines wants to merge 7 commits into
mainfrom
nikki-magic-code-followup

Conversation

@NikkiWines

@NikkiWines NikkiWines commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Follow up to #96181 - replaces new instances of magic code usage since that was released

Fixed Issues

$ Tied to #96180
PROPOSAL:

Tests

N/A small find + replace

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

N/A small find + replace

  • Verify that no errors appear in the JS console

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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@NikkiWines
NikkiWines requested a review from chuckdries July 30, 2026 11:17
@NikkiWines NikkiWines self-assigned this Jul 30, 2026
@NikkiWines
NikkiWines requested review from a team as code owners July 30, 2026 11:17
@melvin-bot
melvin-bot Bot requested review from Valforte and joekaufmanexpensify and removed request for a team July 30, 2026 11:18
@melvin-bot

melvin-bot Bot commented Jul 30, 2026

Copy link
Copy Markdown

@Valforte 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 removed the request for review from a team July 30, 2026 11:18

@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: 1e91c1959e

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

import getWalletPersonalDetailsParams from '@pages/EnablePayments/shared/getWalletPersonalDetailsParams';
import IdologyQuestions from '@pages/EnablePayments/shared/IdologyQuestions';
import useWalletPhoneMagicCode from '@pages/EnablePayments/shared/useWalletPhoneMagicCode';
import useWalletPhoneValidateCode from '@pages/EnablePayments/shared/useWalletPhoneValidateCode';

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Restore the renamed wallet validation modules

This new import points at @pages/EnablePayments/shared/useWalletPhoneValidateCode, but this commit deletes useWalletPhoneMagicCode.ts without adding a useWalletPhoneValidateCode.ts replacement (the shared directory in the reviewed tree has no such file). As soon as the enable-payments personal-details pages or the updated unit test are loaded, module resolution fails and the KYC flow cannot render.

Useful? React with 👍 / 👎.

},
[SCREENS.SETTINGS.WALLET.ENABLE_PAYMENTS_CONFIRM_MAGIC_CODE]: {
path: ROUTES.SETTINGS_ENABLE_PAYMENTS_CONFIRM_MAGIC_CODE.route,
[SCREENS.SETTINGS.WALLET.ENABLE_PAYMENTS_CONFIRM_VALIDATE_CODE]: {

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Register the renamed screen constant before using it

SCREENS.SETTINGS.WALLET.ENABLE_PAYMENTS_CONFIRM_VALIDATE_CODE is not defined in src/SCREENS.ts (the navigator/types/RHP relation still use ENABLE_PAYMENTS_CONFIRM_MAGIC_CODE). In the transpiled app this creates an undefined key in the linking config, so settings/wallet/enable-payments/confirm-validate-code is not mapped to the mounted wallet confirmation screen and navigation to the new URL cannot resolve correctly.

Useful? React with 👍 / 👎.

@NikkiWines

Copy link
Copy Markdown
Contributor Author

@joekaufmanexpensify, this is a follow-up to an existing PR, don't think we need a product review here 🙇

@NikkiWines
NikkiWines removed the request for review from joekaufmanexpensify July 30, 2026 11:42
@codecov

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/CONST/index.ts 94.81% <ø> (ø)
src/ROUTES.ts 22.28% <100.00%> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
...eaderActions/MoneyReportHeaderSecondaryActions.tsx 0.66% <ø> (ø)
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 66.66% <ø> (ø)
src/libs/actions/Wallet.ts 3.44% <ø> (ø)
...nablePayments/shared/useWalletPhoneValidateCode.ts 100.00% <ø> (ø)
...gation/AppNavigator/ModalStackNavigators/index.tsx 6.42% <0.00%> (ø)
...ts/Pay/AdditionalDetails/AdditionalDetailsStep.tsx 0.00% <0.00%> (ø)
... and 3 more
... and 11 files with indirect coverage changes

@NikkiWines NikkiWines changed the title Strip new magic codes instances [HOLD] Strip new magic codes instances Jul 30, 2026
@NikkiWines

Copy link
Copy Markdown
Contributor Author

HELD pending #97278

@NikkiWines NikkiWines changed the title [HOLD] Strip new magic codes instances Strip new magic codes instances Jul 30, 2026
@NikkiWines

Copy link
Copy Markdown
Contributor Author

Off hold now

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.

1 participant