-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Fix #88730: show invite-as-user row for unknown emails in SearchRouter #89405
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
Open
15antonian
wants to merge
8
commits into
Expensify:main
Choose a base branch
from
15antonian:fix/88730-search-invite-user-label
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
0f927a6
Fix #88730: show Invite label for unknown-email results in SearchRouter
15antonian 5736165
Add regression tests for canCreateOptimisticPersonalDetailOption #88730
15antonian d175665
Address Codex P1: also match raw E.164 logins in canCreateOptimisticP…
15antonian 6a3c619
Merge remote-tracking branch 'origin/main' into fix/88730-search-invi…
15antonian d236d83
Add test: invite row shows "Invite" alternateText for unknown email i…
15antonian f0db258
Add UI test: invite row alternateText covered in SearchAutocompleteList
15antonian 126cb5e
Fix ESLint: explicit props on SearchQueryListItem, remove stale disab…
15antonian 27abac1
Revert SearchAutocompleteList to spread props; keep test file ESLint fix
15antonian 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
Oops, something went wrong.
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 these changes?
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.
The react/jsx-props-no-spreading ESLint rule forbids JSX prop spreading the {...props} here caused a CI failure.
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.
Don't see any issues with the pipeline in this place in your previous commits
Do you have this issue locally?
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.
Ran it locally.
npx eslint src/components/Search/SearchAutocompleteList.tsxthrowserror Prop spreading is forbidden react/jsx-props-no-spreadingat line 111. CI also failed on that check in the run right before this fix.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.
Are you sure?
And update node_modules and try recheck, please
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.
You're right, the original had an
eslint-disable-next-linecomment suppressing it. I removed that and replaced the spread with explicit props instead, which is the proper fix rather than suppressing the rule. Happy to revert to the disable comment if preferred.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.
Where? 😅

And I just want to avoid changes that are not related to the fix in our PR
So let's revert these changes
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.
Reverted. My bad that eslint-disable comment was introduced by me in this PR, not from main. Reverted to the plain spread