Skip to content

Add gift card purchase prohibited expense toggle#87534

Merged
dangrous merged 11 commits into
mainfrom
claude-addGiftCardProhibitedExpense
May 12, 2026
Merged

Add gift card purchase prohibited expense toggle#87534
dangrous merged 11 commits into
mainfrom
claude-addGiftCardProhibitedExpense

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds the giftCard toggle to the prohibited expenses UI in workspace rules settings.

  • Added GIFT_CARD to PROHIBITED_EXPENSES in CONST
  • Added giftCard to ProhibitedExpenses type
  • Added toggle label and violation message translations in all 11 language files

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/621672

Tests

  • Verify that no errors appear in the JS console
  • Go to Workspace > Rules > Prohibited expenses
  • Verify "Gift card purchases" toggle appears
  • Toggle it on/off and verify the correct API call is sent with the giftCard key
  • Verify the violation message displays correctly

Offline tests

N/A

QA Steps

  1. Go to Workspace > Rules > Prohibited expenses
  2. Verify "Gift card purchases" toggle appears and functions correctly
  3. Verify violation message displays correctly in all languages
  4. Upload a receipt with a gift card on it and confirm the violation appears when the toggle is on, and does not appear when the toggle is off.

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 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 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)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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 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.
  • 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.
  • 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

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
@MelvinBot MelvinBot requested review from a team as code owners April 9, 2026 19:17
@melvin-bot melvin-bot Bot requested review from heyjennahay and mjasikowski and removed request for a team April 9, 2026 19:17
@melvin-bot

melvin-bot Bot commented Apr 9, 2026

Copy link
Copy Markdown

@mjasikowski 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 April 9, 2026 19:17
@OSBotify

OSBotify commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

The diff is too large to include in this comment (64KB), so I've created a gist for you:

📋 View the translation diff here 📋

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply, or directly by running gh gist view --raw 3a4d607f58fb55b04a45692d3a3aae76 | git apply 😉

View workflow run

@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: 4c41346b1f

ℹ️ 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/languages/it.ts Outdated
case 'adultEntertainment':
return `intrattenimento per adulti`;
case 'hotelIncidentals':
case hotelIncidentals:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P0 Badge Use ASCII quotes in Italian prohibited expense switch

The new case label uses typographic quotes (‘hotelIncidentals’) instead of normal JavaScript string delimiters, which makes src/languages/it.ts invalid syntax and prevents the bundle from parsing this module at build/runtime. Because the translations files are imported as code (not data), this breaks app startup universally until the quotes are changed back to '...' (and the same issue on the added giftCard case should be corrected too).

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This was already fixed in commit f02cee3. The remaining typographic quotes (e.g. dell'hotel) are pre-existing in the main branch for other entries and are not part of this PR's changes.

The original commit introduced Unicode smart quotes (U+2018/U+2019) in
case statement string delimiters in it.ts, which are not valid JavaScript
syntax. This caused Prettier and TypeScript check failures.

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing Prettier and TypeScript checks. The original commit had Unicode smart quotes (U+2018/U+2019) in case statement string delimiters in src/languages/it.ts, which are invalid JavaScript syntax. Replaced them with standard ASCII single quotes.

mjasikowski
mjasikowski previously approved these changes Apr 10, 2026
@mjasikowski

Copy link
Copy Markdown
Contributor

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
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@mjasikowski

Copy link
Copy Markdown
Contributor

@dangrous you'll need to do the author checklist here

@dangrous

Copy link
Copy Markdown
Contributor

Sorry, Melv shouldn't have put this in review yet, we need some other bits and pieces first.

@dangrous dangrous marked this pull request as draft April 10, 2026 19:17
@dangrous dangrous changed the title Add gift card purchase prohibited expense toggle [HOLD Web-E#52007] Add gift card purchase prohibited expense toggle Apr 10, 2026
@dangrous

Copy link
Copy Markdown
Contributor

52007 is waiting on https://github.com/Expensify/Web-Expensify/pull/52006

@dangrous

Copy link
Copy Markdown
Contributor

https://github.com/Expensify/Web-Expensify/pull/52007 is off hold, so this one should be progressing soon

@dangrous dangrous changed the title [HOLD Web-E#52007] Add gift card purchase prohibited expense toggle [HOLD Web-E#52474] Add gift card purchase prohibited expense toggle May 5, 2026
@dangrous

dangrous commented May 6, 2026

Copy link
Copy Markdown
Contributor

https://github.com/Expensify/Web-Expensify/pull/52474 is merged! not yet deployed but then we'll be in business here

@dangrous dangrous changed the title [HOLD Web-E#52474] Add gift card purchase prohibited expense toggle Add gift card purchase prohibited expense toggle May 7, 2026
@dangrous

dangrous commented May 7, 2026

Copy link
Copy Markdown
Contributor

@MelvinBot please merge main, handle conflicts, and also update translations as necessary based on Polyglot Parrot's comment here - #87534 (comment)

@MelvinBot

Copy link
Copy Markdown
Contributor Author

⚠️ Something went wrong. This may be a transient issue — try again. If it persists, check status.anthropic.com.

Run details

@dangrous

dangrous commented May 7, 2026

Copy link
Copy Markdown
Contributor

Try again please @MelvinBot - start just by merging main and resolving comments

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

⚠️ Something went wrong. This may be a transient issue — try again. If it persists, check status.anthropic.com.

Run details

Comment thread src/CONST/index.ts
GAMBLING: 'gambling',
TOBACCO: 'tobacco',
ADULT_ENTERTAINMENT: 'adultEntertainment',
GIFT_CARD: 'giftCard',

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-3 (docs)

giftCard was added to CONST.POLICY.PROHIBITED_EXPENSES but is missing from CONST.POLICY.DEFAULT_PROHIBITED_EXPENSES (line ~3909). Every other prohibited expense type (alcohol, hotelIncidentals, gambling, tobacco, adultEntertainment, handwrittenReceipt) has an entry in both objects. This omission causes PolicyUtils.ts (line ~809) to skip giftCard when checking whether prohibited expenses differ from defaults, meaning enabling the gift card toggle will not be detected as a non-default rule change.

Add giftCard: false to DEFAULT_PROHIBITED_EXPENSES:

DEFAULT_PROHIBITED_EXPENSES: {
    alcohol: false,
    hotelIncidentals: false,
    gambling: true,
    tobacco: false,
    adultEntertainment: true,
    giftCard: false,
    handwrittenReceipt: false,
},

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

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.

@MelvinBot please update this

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Added giftCard: false to DEFAULT_PROHIBITED_EXPENSES in e885ca7.

Adds the missing giftCard: false entry to DEFAULT_PROHIBITED_EXPENSES
so that enabling the gift card toggle is detected as a non-default
rule change by PolicyUtils.

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

⚠️ MelvinBot CI Fix Loop Detected

MelvinBot has made 5 consecutive commits trying to fix CI failures. Automatic CI fix dispatches are now paused for this PR.

Next steps: A human should review the recent commits and resolve the conflicting CI errors manually.

@dangrous

Copy link
Copy Markdown
Contributor

@MelvinBot can you fix the typecheck? Unrelated but helpful

The property was removed from TypeMenuSectionsParams but the test
still passed it, causing a typecheck failure.

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the typecheck failure: removed stale shouldRedirectToExpensifyClassic property from SearchUIUtilsTest.ts:7082 — the property was removed from TypeMenuSectionsParams but the test still referenced it.

MelvinBot and others added 2 commits May 11, 2026 17:28
This property was removed from TypeMenuSectionsParams but the test
still referenced it, causing a typecheck failure.

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
…com/Expensify/App into claude-addGiftCardProhibitedExpense

Co-authored-by: Daniel Gale-Rosen <dangrous@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing typecheck: removed shouldRedirectToExpensifyClassic from the test in SearchUIUtilsTest.ts — this property was removed from TypeMenuSectionsParams on main but the test still referenced it.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

The ESLint check failure is unrelated to this PR.

All 6 errors are in src/pages/ReimbursementAccount/USD/ files that are not touched by this PR:

  • 5x useSubStep deprecation errors (BankInfo.tsx, BeneficialOwnersStep.tsx, BusinessInfo.tsx, CompleteVerification.tsx, PersonalInfo.tsx)
  • 1x namespace import error (ConfirmationUBO.tsx)

This PR only changes: src/CONST/index.ts, language files, IndividualExpenseRulesSection.tsx, Policy.ts, and SearchUIUtilsTest.ts — none of the failing files.

These are pre-existing lint errors on main, likely introduced by a recent merge. Re-running the check or waiting for a main fix should resolve this.

@dangrous

Copy link
Copy Markdown
Contributor

why are there suddenly so many unrelated things? ugh.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

The ESLint check failure is unrelated to this PR's changes.

Evidence: This PR modifies files in src/pages/workspace/rules/, src/CONST/, src/languages/, and src/types/onyx/. The 6 ESLint errors are all in src/pages/ReimbursementAccount/USD/ — none of which are touched by this PR:

  • ConfirmationUBO.tsx:6 — namespace import from @libs not allowed (no-restricted-syntax)
  • useSubStep deprecation errors in BankInfo.tsx, BeneficialOwnersStep.tsx, BusinessInfo.tsx, CompleteVerification.tsx, PersonalInfo.tsx

These are pre-existing lint errors on main that this PR's branch inherited.

@dangrous

Copy link
Copy Markdown
Contributor

okay well @mjasikowski this is ready for review, eslint is unrelated and I'll merge it out at some point hopefully...

@mjasikowski

Copy link
Copy Markdown
Contributor

@dangrous looks good!

@dangrous dangrous merged commit abe92c2 into main May 12, 2026
33 checks passed
@dangrous dangrous deleted the claude-addGiftCardProhibitedExpense branch May 12, 2026 14:15
@OSBotify

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/dangrous in version: 9.3.73-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Yes, help site changes are required. The PR adds a new "Gift card purchases" prohibited expense toggle, but the two help site articles listing prohibited expense categories don't include it.

Draft PR created: #90425

Changes made:

  • Prohibited-Expense-Rule.md — Added "Gift card purchases" to the category list, updated description and keywords
  • Workspace-Rules.md — Added "Gift card purchases" to the prohibited expenses category list

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/dangrous in version: 9.3.73-0 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.73-4 🚀

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

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.

5 participants