[NoQA] Add HR and Gusto foundation by ShridharGoel · Pull Request #87689 · Expensify/App

ShridharGoel · 2026-04-11T04:07:28Z

Explanation of Change

Adds the foundation for HR and Gusto. This includes shared constants, policy/API types, routes, navigation/linking entries, optimistic HR enable action, HR page open action, Gusto sync result types, and HR connection grouping.

Fixed Issues

$ #87007
PROPOSAL: N/A

Tests

Verify that no errors appear in the JS console

Offline 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-04-11T04:07:34Z

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:

Look at the code and make sure there are no malicious changes.
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

codecov · 2026-04-11T04:47:01Z

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	`93.65% <ø> (ø)`
src/SCREENS.ts	`100.00% <ø> (ø)`
src/libs/API/types.ts	`100.00% <ø> (ø)`
...gation/linkingConfig/RELATIONS/WORKSPACE_TO_RHP.ts	`100.00% <ø> (ø)`
src/libs/Navigation/linkingConfig/config.ts	`76.92% <ø> (ø)`
src/libs/ReportActionsUtils.ts	`72.82% <100.00%> (+0.01%)`	⬆️
src/libs/actions/RequestConflictUtils.ts	`98.61% <ø> (ø)`
...ppNavigator/Navigators/WorkspaceSplitNavigator.tsx	`0.00% <0.00%> (ø)`
src/libs/PolicyUtils.ts	`62.30% <50.00%> (+0.08%)`	⬆️
...gation/AppNavigator/ModalStackNavigators/index.tsx	`6.83% <0.00%> (-0.02%)`	⬇️
... and 7 more
... and 11 files with indirect coverage changes

ShridharGoel · 2026-04-11T06:09:50Z

@claude review

melvin-bot · 2026-04-11T06:34:07Z

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

shubham1206agra · 2026-04-11T07:46:05Z

src/CONST/index.ts

+            get ACCOUNTING_CONNECTION_NAMES() {
+                return [this.NAME.QBO, this.NAME.QBD, this.NAME.XERO, this.NAME.NETSUITE, this.NAME.SAGE_INTACCT, this.NAME.CERTINIA] as const;
+            },
+            get HR_CONNECTION_NAMES() {
+                return [this.NAME.GUSTO] as const;
+            },


@ShridharGoel Can you extract this part in a separate PR? It will be easier to review in parts.

Actually the commits are organised, does reviewing each commit one-by-one help? Else I can move it to a new PR but wanted to check first.

@ShridharGoel Move it to a new PR

ShridharGoel · 2026-04-11T10:26:22Z

Updated

melvin-bot bot assigned ShridharGoel Apr 11, 2026

ShridharGoel changed the title ~~Add shared HR and Gusto workspace support~~ [NoQA] Add shared HR and Gusto workspace support Apr 11, 2026

ShridharGoel changed the title ~~[NoQA] Add shared HR and Gusto workspace support~~ [NoQA] Add HR and Gusto foundation Apr 11, 2026

ShridharGoel force-pushed the gusto1.2 branch from 14f01fc to 8e0eb41 Compare April 11, 2026 06:08

ShridharGoel marked this pull request as ready for review April 11, 2026 06:34

ShridharGoel requested review from a team as code owners April 11, 2026 06:34

melvin-bot bot requested review from shubham1206agra and trjExpensify April 11, 2026 06:34

melvin-bot bot removed request for a team April 11, 2026 06:34

shubham1206agra reviewed Apr 11, 2026

View reviewed changes

ShridharGoel added 4 commits April 11, 2026 15:30

Add Gusto constants and API types

11ee8d7

Add HR workspace routes and labels

8f69925

Add HR policy actions

caf5ee1

Add HR workspace entry points

23e28cd

ShridharGoel force-pushed the gusto1.2 branch from 8e0eb41 to 23e28cd Compare April 11, 2026 10:02

ShridharGoel added 2 commits April 11, 2026 15:44

Merge remote-tracking branch 'upstream/main' into gusto1.2

f303370

Move Gusto policy sync types to grouping PR

632850f

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[NoQA] Add HR and Gusto foundation#87689

[NoQA] Add HR and Gusto foundation#87689
ShridharGoel wants to merge 6 commits intoExpensify:mainfrom
ShridharGoel:gusto1.2

ShridharGoel commented Apr 11, 2026 •

edited

Loading

Uh oh!

melvin-bot bot commented Apr 11, 2026

Uh oh!

codecov bot commented Apr 11, 2026 •

edited by github-actions bot

Loading

Uh oh!

ShridharGoel commented Apr 11, 2026

Uh oh!

melvin-bot bot commented Apr 11, 2026

Uh oh!

shubham1206agra Apr 11, 2026

Uh oh!

ShridharGoel Apr 11, 2026

Uh oh!

shubham1206agra Apr 11, 2026

Uh oh!

ShridharGoel commented Apr 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

ShridharGoel commented Apr 11, 2026 • edited 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 Apr 11, 2026

Uh oh!

codecov bot commented Apr 11, 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!

ShridharGoel commented Apr 11, 2026

Uh oh!

melvin-bot bot commented Apr 11, 2026

Uh oh!

shubham1206agra Apr 11, 2026

Choose a reason for hiding this comment

Uh oh!

ShridharGoel Apr 11, 2026

Choose a reason for hiding this comment

Uh oh!

shubham1206agra Apr 11, 2026

Choose a reason for hiding this comment

Uh oh!

ShridharGoel commented Apr 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

ShridharGoel commented Apr 11, 2026 •

edited

Loading

codecov bot commented Apr 11, 2026 •

edited by github-actions bot

Loading