-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Dismiss modal when closing receipt view #60698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
youssef-lr
merged 5 commits into
Expensify:main
from
bernhardoj:fix/60101-user-navigated-to-report-screen-after-dismissing-receipt-view
May 3, 2025
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we aren't fetching the data from actions. so
canBeMissingshould befalsein all cases here. right??Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bernhardoj see https://expensify.slack.com/archives/C01GTK53T8Q/p1745872527961489?thread_ts=1745579616.289599&cid=C01GTK53T8Q for correct usage
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We load the report here and reportMetadata is updated inside openReport.
App/src/pages/TransactionReceiptPage.tsx
Lines 52 to 60 in 1d48288
For the transactions, I think I intentionally set it to true, as you already experienced, the alert keeps showing for transactions_undefined. It can happen for transactions_0, transactions_123, or any invalid key. I personally don't like the
canBeMissingsince a user can easily open the page without the data available.