-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Stop creating the transaction thread reports optimistically for RequestMoney #58825
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
iwiznia
merged 12 commits into
Expensify:main
from
callstack-internal:VickyStash/feature/stop-creating-optimistic-transaction-RequestMoney
Apr 9, 2025
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
ecbc646
Stop creating the transaction thread reports optimistically for Reque…
VickyStash fd89725
Fix one-transaction-thread checks
VickyStash 7fe128e
Merge branch 'refs/heads/main' into VickyStash/feature/stop-creating-…
VickyStash 6ccf441
Fix tests
VickyStash eb54c2b
Merge branch 'refs/heads/main' into VickyStash/feature/stop-creating-…
VickyStash b7e27ce
Lint fix
VickyStash 3d8ce15
Optimistic transaction thread creation on its open
VickyStash e183c36
Fix transaction thread creation for one transaction thread scenario
VickyStash 5974efe
Minor code improvements
VickyStash 019771b
Merge branch 'refs/heads/main' into VickyStash/feature/stop-creating-…
VickyStash 7efd7c6
Merge branch 'refs/heads/main' into VickyStash/feature/stop-creating-…
VickyStash d8b9097
Move shouldGenerateOptimisticTransactionThread flag inside params object
VickyStash 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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
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.
Why do we need the constant? Can't we use
null
or""
or leaveundefined
which IIRC is what we said when we did not have a string ID?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.
In this specific case, we need to return a truly value, so
null
, '', orundefined
won't work.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.
Why does it need to be truthy?
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.
To explain that, let's take a look at a couple of lines above of the
getOneTransactionThreadReportID
function and what it does.singleAction
constApp/src/libs/ReportActionsUtils.ts
Line 1213 in 8dfbd12
We won't always have the
childReportID
insidesingleAction
now, cause we won't generate the transaction thread report right from the start.But the app should still act with the report as with the one transaction thread report. Handle the navigation and UI in an appropriate way.
That's why in this case we return truly value.
@iwiznia what do you think?
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.
^^ @iwiznia