Skip to content

Conversation

@samranahm
Copy link
Contributor

@samranahm samranahm commented Dec 24, 2025

Explanation of Change

We're adding the Vacation Delegate view for delegates on the Status page.

Fixed Issues

$ #78037
PROPOSAL: #78037 (comment)

Tests

Precondition: User A is not a delegate for anyone.

Steps

  1. User A opens the Status page and selects Vacation Delegate.
  2. User A sets User B as their vacation delegate.
  3. User B opens the Status page.
  4. Verify the following message is displayed:

You can't set a vacation delegate because you're currently the delegate for the following members:

  1. Verify User A is listed.
  2. Verify the “Vacation Delegate” menu item is not shown for User B.
  3. Another user sets User B as their vacation delegate.
  4. Verify all users who delegated to User B are listed.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 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.

Will add the Screenshots/Videos of remaining platforms once the BE update deployed.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS.Chrome.mp4

Copilot AI review requested due to automatic review settings December 24, 2025 19:10
@samranahm samranahm requested review from a team as code owners December 24, 2025 19:10
@melvin-bot melvin-bot bot requested review from Beamanator and huult December 24, 2025 19:10
@melvin-bot
Copy link

melvin-bot bot commented Dec 24, 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

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds a vacation delegate view for users who are currently acting as delegates for other members. When a user is set as a vacation delegate by others, they cannot set their own vacation delegate, and instead see a list of all members who have delegated to them.

Key Changes:

  • Added delegatorFor field to VacationDelegate type to track users delegating to the current user
  • Implemented conditional rendering in StatusPage to show delegator list when user has active delegations
  • Added translations for the "cannot set vacation delegate" message across all supported languages

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
src/types/onyx/VacationDelegate.ts Added delegatorFor field to track array of delegator emails
src/pages/settings/Profile/CustomStatus/StatusPage.tsx Added conditional UI to display delegators list or vacation delegate settings based on delegation status
src/languages/en.ts Added English translation for "cannot set vacation delegate" message
src/languages/es.ts Added Spanish translation
src/languages/de.ts Added German translation
src/languages/fr.ts Added French translation
src/languages/it.ts Added Italian translation
src/languages/ja.ts Added Japanese translation
src/languages/nl.ts Added Dutch translation
src/languages/pl.ts Added Polish translation
src/languages/pt-BR.ts Added Portuguese (Brazil) translation
src/languages/zh-hans.ts Added Chinese (Simplified) translation

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov
Copy link

codecov bot commented Dec 24, 2025

Codecov Report

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

Files with missing lines Coverage Δ
...ings/Profile/CustomStatus/VacationDelegatePage.tsx 0.00% <0.00%> (ø)
...pages/settings/Profile/CustomStatus/StatusPage.tsx 0.00% <0.00%> (ø)
... and 17 files with indirect coverage changes

@huult
Copy link
Contributor

huult commented Dec 26, 2025

Weird, Melvin bot added many reviewers

@huult
Copy link
Contributor

huult commented Dec 26, 2025

Link to Slack message:

@samranahm You missed the link to the Slack message in the checklist

@huult
Copy link
Contributor

huult commented Dec 26, 2025

@samranahm Please fill in the QA steps as well

{hasActiveDelegations ? (
<View>
<Text style={[styles.mh5, styles.mb4]}>{translate('statusPage.cannotSetVacationDelegate')}</Text>
{vacationDelegate?.delegatorFor?.map((delegatorEmail) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest refactoring this block into renderDelegatorList() as shown, adding a null guard and simplifying variable names for readability.

Example:

const renderDelegatorList = () => {
    if (!vacationDelegate?.delegatorFor) {
        return null;
    }

    return vacationDelegate.delegatorFor.map((delegatorEmail) => {
        const delegatorDetails = getPersonalDetailByEmail(delegatorEmail);
        const formattedLogin = formatPhoneNumber(delegatorDetails?.login ?? '');
        const displayLogin = formattedLogin || delegatorEmail;

        return (
            <MenuItem
                key={delegatorEmail}
                title={delegatorDetails?.displayName ?? displayLogin}
                description={displayLogin}
                avatarID={delegatorDetails?.accountID ?? CONST.DEFAULT_NUMBER_ID}
                icon={delegatorDetails?.avatar ?? Expensicons.FallbackAvatar}
                iconType={CONST.ICON_TYPE_AVATAR}
                numberOfLinesDescription={1}
                containerStyle={[styles.pr2, styles.mt1]}
                interactive={false}
            />
        );
    });
};

....


{renderDelegatorList()}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, These changes indeed make the component cleaner and more maintainable. I’ll refactor it accordingly.

@samranahm
Copy link
Contributor Author

@huult Please take a look.

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.

2 participants