-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$500][MEDIUM] Categories: Search field is present in category list when there are fewer than 8 categories to choose from #37329
Comments
Job added to Upwork: https://www.upwork.com/jobs/~0110ba1eec3b905bcd |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @akinwale ( |
Triggered auto assignment to @sonialiap ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @jasperhuangg ( |
We think that this bug might be related to #wave6 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Search field is present in Category list when there is less than 8 categories What is the root cause of that problem?We don't pass shouldShowTextInput to the selection list in What changes do you think we should make in order to solve the problem?We should add the
Then pass this variable to
Then pass this prop: shouldShowTextInput={showInput} |
Regression of this #35567. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Search field is present in Category list when there is less than 8 categories What is the root cause of that problem?The variable name policyCategoriesCount is wrong:
What changes do you think we should make in order to solve the problem?Replace the above with:
What alternative solutions did you explore? (Optional)N/A |
Definitely a bug, but doesn't need to block the deploy. Removing the label. |
Waiting for proposals |
I already proposed a solution above, can you please have a look :)
…On Sat, Mar 2, 2024 at 12:25 AM Jasper Huang ***@***.***> wrote:
Waiting for proposals
—
Reply to this email directly, view it on GitHub
<#37329 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BFJXGI6YMLNWCLXOSU4UJBLYWDFLFAVCNFSM6AAAAABD4R7SFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTG42TCMJQHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I am unable to reproduce this. Seems it has already been fixed on main. App/src/components/CategoryPicker.tsx Line 67 in 4231ac9
|
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.44-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Precondition:
Expected Result:
There will be no search field because there are less than 8 categories
Actual Result:
Search field is present when there are less than 8 categories
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6394369_1709055952133.20240227-141548-1_kEAvasRf.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: