Skip to content

Conversation

@NJ-2020
Copy link
Contributor

@NJ-2020 NJ-2020 commented Oct 11, 2025

Explanation of Change

Add validation to prevent formulas from referencing themselves

Fixed Issues

$ #70775
PROPOSAL: #70775 (comment)

Tests

  1. Create a workspace if needed
  2. Go to workspace settings, Reports, enable report fields if needed

Initial/Default value

Self Reference

  1. Create new report field named "A"
  2. Attempt to set it's initial value to "{field:A}"
  3. Verify an error is displayed and you can't save that value

Circular Reference

2 circular/references

  1. Create new report field named "A"
  2. Set it's initial value to "{field:B}" (make sure {field:B} or field B is not created yet)
  3. Verify you can save/create the field
  4. Create new report field named "B"
  5. Attempt to set it's initial value to "{field:A}"
  6. Verify an error is displayed and you can't save that value

More than 2 circular/references

  1. Create new report field named "A"
  2. Set it's initial value to "{field:B}" (make sure {field:B} or field B is not created yet)
  3. Verify you can save/create the field
  4. Create new report field named "B"
  5. Set it's initial value to "{field:C}" (make sure {field:C} or field C is not created yet)
  6. Create new report field named "C"
  7. Attempt to set it's initial value to "{field:A}"
  8. Verify an error is displayed and you can't save that value

No references

  1. Create new report field named "A"
  2. Set it's initial value to "{field:B}" (make sure {field:B} is created and the default/initial value is set to empty > "" or no formula circular field)
  3. Verify you can save/create the field

Report field value / report expense

  1. Go to workspace expenses chat
  2. Select/Open any report
  3. Edit the report field value
  4. Type formula value that references itself/circular reference i.e A, A > A, A > B > A
  5. Verify an error is displayed and you can't save that value
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests

QA Steps

Same as Tests

  • 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
    • MacOS: Desktop
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
Screen.Recording.2025-10-16.at.10.online-video-cutter.com.mp4
Android: mWeb Chrome
Screen.Recording.2025-10-16.at.09.49.55.mp4
iOS: Native
Screen.Recording.2025-10-16.at.10.44.52.mp4
iOS: mWeb Safari
Screen.Recording.2025-10-16.at.10.49.38.mp4
MacOS: Chrome / Safari
Screen.Recording.2025-10-16.at.09.25.18.mp4
MacOS: Desktop
Screen.Recording.2025-10-16.at.09.18.15.mp4

@codecov
Copy link

codecov bot commented Oct 11, 2025

Codecov Report

❌ Patch coverage is 69.23077% with 12 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/libs/Formula.ts 81.81% 6 Missing ⚠️
src/pages/EditReportFieldText.tsx 0.00% 3 Missing ⚠️
...workspace/reports/ReportFieldsInitialValuePage.tsx 0.00% 2 Missing ⚠️
...pages/workspace/reports/CreateReportFieldsPage.tsx 0.00% 1 Missing ⚠️
Files with missing lines Coverage Δ
src/pages/EditReportFieldPage.tsx 0.00% <ø> (ø)
...pages/workspace/reports/CreateReportFieldsPage.tsx 0.00% <0.00%> (ø)
...workspace/reports/ReportFieldsInitialValuePage.tsx 0.00% <0.00%> (ø)
src/pages/EditReportFieldText.tsx 0.00% <0.00%> (ø)
src/libs/Formula.ts 84.16% <81.81%> (-0.35%) ⬇️

... and 11 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@NJ-2020
Copy link
Contributor Author

NJ-2020 commented Oct 11, 2025

I'll add unit test soon

@NJ-2020 NJ-2020 marked this pull request as ready for review October 16, 2025 04:17
@NJ-2020 NJ-2020 requested a review from a team as a code owner October 16, 2025 04:17
@melvin-bot melvin-bot bot requested review from DylanDylann and dubielzyk-expensify and removed request for a team October 16, 2025 04:17
@melvin-bot
Copy link

melvin-bot bot commented Oct 16, 2025

@dubielzyk-expensify @DylanDylann One of you needs to 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]

@dubielzyk-expensify
Copy link
Contributor

Videos are looking good to me 👍

@neil-marcellini
Copy link
Contributor

I have bumped in Slack for a C+ review

@neil-marcellini neil-marcellini requested review from abzokhattab and removed request for DylanDylann October 27, 2025 14:04
@abzokhattab
Copy link
Contributor

Reviewing ...

@abzokhattab
Copy link
Contributor

abzokhattab commented Oct 27, 2025

@NJ-2020 I get this error in the second test. Do you also have it?

Screen.Recording.2025-10-27.at.17.18.51.mov
Error: undefined was not found in the en locale

The above error occurred in the <WorkspaceReportFieldsPage> component.

Can you please merge from main? and see if you still have the issue?

@neil-marcellini neil-marcellini requested review from DylanDylann and removed request for abzokhattab October 27, 2025 22:02
@melvin-bot
Copy link

melvin-bot bot commented Oct 28, 2025

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. If you want to automatically generate translations for other locales, you can run the Generate static translations GitHub workflow.

Please look at the code and make sure there are no malicious changes before running the workflow.

If you have the K2 extension, you can simply click: [this button]

@NJ-2020
Copy link
Contributor Author

NJ-2020 commented Oct 28, 2025

Can you please merge from main? and see if you still have the issue?

@abzokhattab Done, fixed ☑️

Screen.Recording.2025-10-28.at.10.42.15.mov

@DylanDylann
Copy link
Contributor

We just added a new formula type. Today I will check again to see if there is any conflict with our change


const hasAccountingConnections = hasAccountingConnectionsPolicyUtils(policy);
const reportField = policy?.fieldList?.[getReportFieldKey(reportFieldID)] ?? null;

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change

Copy link
Contributor Author

Choose a reason for hiding this comment

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

☑️

});
}

if (type === CONST.REPORT_FIELD_TYPES.TEXT && hasCircularReferences(formInitialValue, name, policy?.fieldList)) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Also need to check hasCircularReferences for fomula type

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done ☑️

Comment on lines +205 to +210
if (!fieldList || isEmptyObject(fieldList)) {
return formulaValues.some((formula) => {
const fieldPath = parsePart(formula).fieldPath;
return fieldPath.includes(fieldName);
});
}
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks redundant because we always have a default report field

}

// Get the referenced field name (first element in fieldPath)
const referencedFieldName = part.fieldPath.at(0);
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const referencedFieldName = part.fieldPath.at(0);
const referencedFieldName = part.fieldPath.at(0)?.trim();

Copy link
Contributor

Choose a reason for hiding this comment

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

It works if we enter {field:A} but doesn't work if we enter {field: A}

--> need to trim the value

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍, Done ☑️

if (referencedField?.defaultValue) {
// Recursively check the referenced field
if (hasCircularReferencesRecursive(referencedField.defaultValue, referencedFieldName)) {
visitedLists.delete(currentFieldName);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we need to delete the value in Set?

Copy link
Contributor

Choose a reason for hiding this comment

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

The visitedLists Set is function-scoped and short‑lived; it’s garbage‑collected after hasCircularReferences returns. @NJ-2020 Please correct me if you intend to do that for some reason?

/**
* Check if the report field formula value is containing circular references, e.g example: A -> A, A->B->A, A->B->C->A, etc
*/
function hasCircularReferences(fieldValue: string, fieldName: string, fieldList?: FieldList) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Please add returned type

Suggested change
function hasCircularReferences(fieldValue: string, fieldName: string, fieldList?: FieldList) {
function hasCircularReferences(fieldValue: string, fieldName: string, fieldList?: FieldList): boolean {

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, done ☑️

return true;
}

const referencedField = Object.values(fieldList).find((field) => field.name === referencedFieldName);
Copy link
Contributor

Choose a reason for hiding this comment

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

We can optimize this by creating a Map outside hasCircularReferencesRecursive function

    const fieldsByName = new Map<string, {name: string; defaultValue: string}>(
        Object.values(fieldList).map((field) => [field.name, field]),
    );

and in here we should use get method

const referencedField = fieldsByName.get(referencedFieldName);

Copy link
Contributor

Choose a reason for hiding this comment

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

This reduces per-lookup from O(n) to O(1).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, done ☑️

@DylanDylann
Copy link
Contributor

@NJ-2020 Left some comment

cc @neil-marcellini

@melvin-bot
Copy link

melvin-bot bot commented Nov 1, 2025

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@NJ-2020
Copy link
Contributor Author

NJ-2020 commented Nov 1, 2025

Confirming 🇪🇸 translation here: https://expensify.slack.com/archives/C01GTK53T8Q/p1761983344629779

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