Skip to content

Add coloured labels to report statuses in New Expensify#71751

Merged
lakchote merged 9 commits into
Expensify:mainfrom
lorretheboy:feat/71549
Oct 13, 2025
Merged

Add coloured labels to report statuses in New Expensify#71751
lakchote merged 9 commits into
Expensify:mainfrom
lorretheboy:feat/71549

Conversation

@lorretheboy

@lorretheboy lorretheboy commented Oct 2, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #71549
PROPOSAL: #71549 (comment)

Tests

Prerequisite: User has several reports with different statuses

  1. Go to ND
  2. Go to Reports --> Chats
  3. Verify that there is a status badge in expense message card
  4. Go to Reports
  5. Verify that there is a status badge for every report preview
  6. Click to view report details
  7. Verify that there is a status badge in report header
  8. Verify that status badge's color is updated correctly after changing them from white to dark
  • 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 image image
ANDROID.mov
Android: mWeb Chrome image
WEBSITE.ANDROID.mov
iOS: Native image image image
IOS.mov
iOS: mWeb Safari image
WEBSITE.IOS.mov
MacOS: Chrome / Safari image image image
WEBSITE.mov
MacOS: Desktop image
DESKTOP.mov

@codecov

codecov Bot commented Oct 2, 2025

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 26.66667% with 22 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/libs/ReportUtils.ts 23.52% 13 Missing ⚠️
src/components/ParentNavigationSubtitle.tsx 0.00% 8 Missing ⚠️
src/components/AvatarWithDisplayName.tsx 0.00% 1 Missing ⚠️
Files with missing lines Coverage Δ
...ReportPreview/MoneyRequestReportPreviewContent.tsx 58.18% <100.00%> (+0.60%) ⬆️
src/styles/index.ts 45.35% <ø> (ø)
src/styles/theme/themes/dark.ts 100.00% <ø> (ø)
src/styles/theme/themes/light.ts 100.00% <ø> (ø)
src/components/AvatarWithDisplayName.tsx 1.96% <0.00%> (-0.04%) ⬇️
src/components/ParentNavigationSubtitle.tsx 7.14% <0.00%> (-0.55%) ⬇️
src/libs/ReportUtils.ts 73.69% <23.52%> (-0.23%) ⬇️

... and 6 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.

@lorretheboy lorretheboy marked this pull request as ready for review October 3, 2025 17:38
@lorretheboy lorretheboy requested review from a team as code owners October 3, 2025 17:38
@melvin-bot melvin-bot Bot requested review from suneox and removed request for a team October 3, 2025 17:38
@melvin-bot

melvin-bot Bot commented Oct 3, 2025

Copy link
Copy Markdown

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

@dannymcclain

Copy link
Copy Markdown
Contributor

@Expensify/design I think with the introduction of these colored badges we should ditch any of the icons associated with status (check for paid & thumbs up for approved). What do you all think?

CleanShot 2025-10-03 at 12 43 08@2x

@shawnborton

Copy link
Copy Markdown
Contributor

I totally agree with that - let's kill them.

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

Yeah agree. Looks funky with them.

@shawnborton

Copy link
Copy Markdown
Contributor

@lorretheboy can you please make those changes and then we can spin up some test builds for further testing? Thanks!

@lorretheboy

Copy link
Copy Markdown
Contributor Author

Sure @shawnborton

@lorretheboy

Copy link
Copy Markdown
Contributor Author

@suneox I have updated the code to address new requirements. Could u please help review again? Thx

@github-actions

github-actions Bot commented Oct 6, 2025

Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@dannymcclain

Copy link
Copy Markdown
Contributor

🤔 the text looks quite small—can you double check that it's using our micro size?

CleanShot 2025-10-06 at 14 32 19@2x CleanShot 2025-10-06 at 14 31 43@2x

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

Agree with that. Feels very small

@shawnborton

Copy link
Copy Markdown
Contributor

Yup, looks like the font size is wrong. Let's fix that and then we can spin up a new test build.

@lorretheboy

Copy link
Copy Markdown
Contributor Author

Hi team, please correct me in case I miss understand anything. As far as I see in the design, we set font size is 11px and the badge height is 16px. So that the badge and the text next to it has the same height

However, in some small screen, to make the badge and the text next to it has the same height we have to reduce the size of the text as well as the badge height. Can we agree that we have to reduce the size in cases that screen size is small?

Besides, I agree that the the font size I am using here fontSizeXSmall which has the range from 8px to 12px doesn't work well. I will try to find the better range for it

Thanks

image

@shawnborton

Copy link
Copy Markdown
Contributor

I think we want to use the exact same height and font size for the badge at all screen sizes. Please refer to the mocks we provided on the issue for size guidance.

Comment thread src/styles/index.ts Outdated
},

reportStatusText: {
fontSize: variables.fontSizeXSmall,

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.

We have to update the style based on the design and confirmation from the design team.

Suggested change
fontSize: variables.fontSizeXSmall,
fontSize: variables.fontSizeSmall,
lineHeight: variables.lineHeightSmall

@shawnborton

Copy link
Copy Markdown
Contributor

Yeah, let's keep the momentum up on this one please. Thanks!

@dannymcclain

Copy link
Copy Markdown
Contributor

I’d be fine just using 16px for the line height to match the container.

Same - I think for this specific component it's ok to just set the line-height to whatever makes the component work best.

@lorretheboy

Copy link
Copy Markdown
Contributor Author

Thanks for the confirmation

I have updated the line height @suneox Please help review it again

@shawnborton

Copy link
Copy Markdown
Contributor

Thanks! I will run test builds again but let's get it into final review.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #71751.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/71751/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/71751/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/71751/NewExpensify.dmg https://71751.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@dannymcclain

Copy link
Copy Markdown
Contributor

Builds are looking good to me 👍

@suneox

suneox commented Oct 10, 2025

Copy link
Copy Markdown
Contributor

I'm not sure if this is a Safari 26.0.1 issue — it’s still not vertically centered on my device. The only fix that works for me is either removing the line height or setting it to an odd value close to the font size.

Screen.Recording.2025-10-11.at.00.27.48.mov

However, since the current change has been verified and works on almost all devices with the existing value so we can go ahead with it.

Comment thread src/styles/index.ts Outdated
reportStatusText: {
fontSize: variables.fontSizeSmall,
fontWeight: FontUtils.fontWeight.normal,
lineHeight: 16,

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.

Please resolve the conflicts and use variables

Suggested change
lineHeight: 16,
lineHeight: variables.lineHeightSmall,

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.

@lorretheboy We can remove the line height in this case, as confirmed

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.

@suneox I have fixed it. Please check again

@dannymcclain

Copy link
Copy Markdown
Contributor

I'm not sure if this is a Safari 26.0.1 issue — it’s still not vertically centered on my device. The only fix that works for me is either removing the line height or setting it to an odd value close to the font size.

Dang, just tested in Safari and I do see the same thing as you. Removing the line-height altogether seems to fix it like you mentioned, and also doesn't seem to cause any issues in other browsers. @Expensify/design do you think we should live with the Safari discrepancy or try just straight up removing the line-height entirely?

@shawnborton

Copy link
Copy Markdown
Contributor

Hmm yeah, just tried playing around with it too and I can't seem to make it work with the line height. I would be down to just remove the line height here since that seems to fix things.

@github-actions

Copy link
Copy Markdown
Contributor

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

@github-actions

Copy link
Copy Markdown
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #71751.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/71751/index.html https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/71751/index.html
Android iOS
Desktop 💻 Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/71751/NewExpensify.dmg https://71751.pr-testing.expensify.com
Desktop Web

👀 View the workflow run that generated this build 👀

@shawnborton

Copy link
Copy Markdown
Contributor

Seems to work well in Safari for me now. Let's get this into final review please!

@melvin-bot melvin-bot Bot requested a review from lakchote October 13, 2025 15:23
@lakchote

Copy link
Copy Markdown
Contributor

Proceeding with the merge since it works well in Safari now

@lakchote lakchote merged commit f0baf7d into Expensify:main Oct 13, 2025
23 checks passed
@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.

@shawnborton

Copy link
Copy Markdown
Contributor

cc @puneetlath - let's make sure we communicate this internally before it goes live?

@puneetlath

Copy link
Copy Markdown
Contributor

Sounds good. @kadiealexander can you please help with that?

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/lakchote in version: 9.2.30-0 🚀

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

@kadiealexander

Copy link
Copy Markdown
Contributor

Posted an update here!

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.30-6 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 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.

9 participants