Skip to content

[Performance] Read Spotnana tripData from report NVPs - #100872

Merged
blimpich merged 7 commits into
mainfrom
rodrigo-680660-tripdata-rnvp
Sep 10, 2026
Merged

blimpich merged 7 commits into
mainfrom
rodrigo-680660-tripdata-rnvp

Conversation

@rlinoz

@rlinoz rlinoz commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Moves Spotnana tripData reads from reports to their corresponding report name-value-pairs, so App is ready for Auth to stop duplicating the payload in report data.

This is also fixing the Upcoming travel section in the home tab, by looking at the traveler instead of the owner of the trip chat.

related auth pr: https://github.com/Expensify/Auth/pull/24416

Fixed Issues

https://github.com/Expensify/Expensify/issues/680660
PROPOSAL:

Tests

  1. Book a trip
  2. Verify it shows up in Home > upcoming travel
  3. Verify the trip preview in the policy expense chat is correctly displayed
  4. Verify the details in the trip chat are correct
Screenshot 2026-09-10 at 15 59 42 Screenshot 2026-09-10 at 16 00 09 Screenshot 2026-09-10 at 16 00 05 Screenshot 2026-09-10 at 16 00 21
  • Verify that no errors appear in the JS console

Offline tests

  1. Disconnect the network after a trip room and its report name-value-pair data have loaded.
  2. Open Home and the Inbox trip preview.
  3. Verify the existing trip details remain visible.

QA Steps

  1. Book a trip
  2. Verify it shows up in Home > upcoming travel
  3. Verify the trip preview in the policy expense chat is correctly displayed
  4. Verify the details in the trip chat are correct
  • 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 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

@codecov

codecov Bot commented Sep 10, 2026

Copy link
Copy Markdown

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 Δ
...rc/components/ReportActionItem/TripDetailsView.tsx 77.22% <100.00%> (+0.22%) ⬆️
...rc/components/ReportActionItem/TripRoomPreview.tsx 57.33% <100.00%> (+0.57%) ⬆️
src/libs/ReportUtils.ts 87.25% <ø> (+0.01%) ⬆️
...mingTravelSection/useUpcomingTravelReservations.ts 100.00% <100.00%> (ø)
src/selectors/Report.ts 83.76% <ø> (ø)
src/libs/DebugUtils.ts 69.09% <0.00%> (ø)
src/libs/TripReservationUtils.ts 81.45% <87.50%> (-0.41%) ⬇️
...c/components/ReportActionItem/MoneyRequestView.tsx 79.86% <77.77%> (+0.49%) ⬆️
src/pages/Travel/DynamicTripSummaryPage.tsx 0.00% <0.00%> (ø)
src/pages/Travel/DynamicTripDetailsPage.tsx 0.00% <0.00%> (ø)
... and 93 files with indirect coverage changes

@rlinoz
rlinoz requested a review from blimpich September 10, 2026 19:01
@rlinoz
rlinoz marked this pull request as ready for review September 10, 2026 19:01
@rlinoz
rlinoz requested review from a team as code owners September 10, 2026 19:01
@melvin-bot
melvin-bot Bot requested review from garrettmknight and removed request for a team September 10, 2026 19:01
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 10, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-10T19:14:37.011998Z c25de01 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot
melvin-bot Bot requested review from jasperhuangg and removed request for a team September 10, 2026 19:02
@melvin-bot

melvin-bot Bot commented Sep 10, 2026

Copy link
Copy Markdown

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

@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: c25de01534

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/components/ReportActionItem/MoneyRequestView.tsx Outdated
Comment on lines +47 to +50
if (!isCurrentUserTraveler(reportNameValuePairs, currentUserEmail)) {
continue;
}
const reservations = getReservationsFromTripReport(report);
const reservations = getReservationsFromTripReport(report, reportNameValuePairs);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Filter reservations to the matching traveler

When a trip contains separate PNRs for the current user and other travelers, this report-level check succeeds because the user appears in any one PNR, but getReservationsFromTripReport() then returns reservations from every PNR in the payload. Consequently, Home can list another traveler's flights or hotels alongside the current user's reservations. Filter the payload or returned reservations by the PNRs whose traveler list contains currentUserEmail.

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.

That was the case before already

@blimpich blimpich left a comment

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.

LGTM!

@blimpich
blimpich merged commit 0fe4731 into main Sep 10, 2026
43 of 44 checks passed
@blimpich
blimpich deleted the rodrigo-680660-tripdata-rnvp branch September 10, 2026 23:16
@github-actions

Copy link
Copy Markdown
Contributor

🚧 blimpich 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/blimpich in version: 9.4.77-0 🚀

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

@MelvinBot

MelvinBot commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Yes — one help site article needed an update. Draft PR: #101001

Why

Most of this PR is an internal data-source refactor (reading tripData from report name-value-pairs instead of report data), which has no help site impact. But one change is user-visible:

src/pages/home/UpcomingTravelSection/useUpcomingTravelReservations.ts now filters Upcoming travel by whether you're a traveler on the booking, replacing the old report.ownerAccountID !== accountID owner check. Trips booked for you now appear; trips you booked for someone else no longer do.

On checking the docs, the Upcoming travel section wasn't documented at all — Expensify-Home-Overview.md lists every other Home section but omits it.

What the draft PR changes

One file, docs/articles/new-expensify/getting-started/Expensify-Home-Overview.md:

  • Adds Upcoming travel to the section list under What Home shows
  • Adds ## How the Upcoming travel section works on Home — the 7-day window, the traveler-based filter, the row format, canceled reservations, and what selecting a row does
  • Adds ## Why don’t I see the Upcoming travel section? to the FAQ
  • Extends keywords and internalScope

articles/travel/managing-trips/View-Upcoming-and-Past-Trips.md needed no edit — it documents the Trips view in the travel tool, which this PR doesn't touch. The new section cross-links to it instead.

How I verified the labels and behavior
  • Section title Upcoming travelhomePage.upcomingTravel in src/languages/en.ts:1211
  • 7-day window — CONST.UPCOMING_TRAVEL_WINDOW_DAYS: 7 in src/CONST/index.ts:7094
  • Row copy (Flight to, Hotel in, Car rental in, Train to, Today, In 1 day, In 1 week) — homePage.upcomingTravelSection in src/languages/en.ts:1212-1223
  • Canceled label — iou.canceled in src/languages/en.ts:1454, applied via formatCancelledDescription
  • Row tap opens the reservation details — UpcomingTravelItem.tsx handlePress

Live web UI check: the Home tab label is confirmed. The Upcoming travel section itself could not be observed live — the test account has no booked trips, so the section doesn't render. The behavior described in the article is read from code, not from a live trip, so please sanity-check it against what you saw in your test.


@rlinoz, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review


view run · no recording available

@jponikarchuk

Copy link
Copy Markdown

Deploy Blocker #101054 was identified to be related to this PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.77-4 🚀

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

Bundle Size Analysis (Sentry):

@sentry

sentry Bot commented Sep 15, 2026

Copy link
Copy Markdown

Issues attributed to commits in this pull request

This pull request was merged and Sentry observed the following issues:

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