-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Fix thread parent message comment linking bug #40344
Closed
FitseTLT
wants to merge
5
commits into
Expensify:main
from
FitseTLT:fix-thread-parent-message-comment-linking-bug
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
6b716a3
change comment link for parent message to link to the parent report
FitseTLT 93b7bdb
fixed expense report case bug
FitseTLT 8dce9db
replaced with getOriginalReportID
FitseTLT 7bd7396
Merge branch 'main' into fix-thread-parent-message-comment-linking-bug
FitseTLT 0d0cb5c
Merge branch 'main' into fix-thread-parent-message-comment-linking-bug
FitseTLT 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 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 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 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 is
transactionThreadReportID
computation blocked under this flag? Shouldn't it break for calls ofgetOriginalReportID
since only one place we are sendingtrue
and others will be false by default?And the change here is different than your original proposal #36057 (comment), could you provide information on how this change is expected to fix the issue?
@FitseTLT
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.
@abdulrahuman5196 I have already commented an explanation for both in Details section on the PR description.
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.
@FitseTLT
This is the from the details section
This is the expected behaviour I get from the issue, but not sure on how it is being fixed with this PR. Because the code change in the proposal is different from the change in this PR. #36057 (comment). Do let me know if there was a different discussion.
What is the UX regression on this issue?, to check if its fixed? I don't see any regression statement in that PR as well its relevant GH. Do add those in test steps if its a specific case.
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.
#36057 (comment) is where the expectation changed that's why the pr is different from the proposal.
Because of the regression caused from #39474 the
reportActionID
part of the link will beundefined
. But the problem it caused is wider as it makes the all context menu operations not to work (like copy to clipboard )