-
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
[HOLD for payment 2023-11-17][$500] XOF currency not searchable by its second term #29345
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~019305a629853b75cc |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.XOF is not searchable using it second term i.e. the text displayed after What is the root cause of that problem?The main problem is that we are looking for a currency without any formatting What changes do you think we should make in order to solve the problem?To fix this bug we can delete all spaces from currencyOptions and searchValue when we filter options App/src/pages/iou/IOUCurrencySelection.js Line 108 in f557852
We can update this line like
App/src/pages/iou/IOUCurrencySelection.js Line 108 in f557852
To be sure that spaces will not interfere with our search Plus It would also be nice to format the string that we use in the search value For this, we can update this line like
App/src/pages/iou/IOUCurrencySelection.js Line 107 in f557852
Also we can use What alternative solutions did you explore? (Optional)NA |
ProposalPlease re-state the problem that we are trying to solve in this issue.XOF currency not searchable by its second term What is the root cause of that problem?This is currency list issue What changes do you think we should make in order to solve the problem?we can update like this.
App/src/pages/iou/IOUCurrencySelection.js Line 108 in f557852
What alternative solutions did you explore? (Optional) |
@abdulrahuman5196 a few proposals to consider here ^^ |
Reviewing now |
How do you plan to do this? Kindly always include the implementation details as part of the proposals. |
@abdulrahuman5196 Thanks for your replyl. |
@yh-0218 This is to be diagnosed by contributor and provide functionality implementation path as part of their changes proposed. Kindly update the proposal with implementation details of the option. |
@abdulrahuman5196 Could you check option2 on my proposal |
@abdulrahuman5196
or
|
@abdulrahuman5196, @laurenreidexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@abdulrahuman5196 what ya reckon ^^ |
@abdulrahuman5196 bump ^ |
Sorry for the delay. Reviewing now |
REviewing now |
All proposals point to whitespace replace during search. I checked and it seems to be simple and effective path forward so going with the first proposal. @ZhenjaHorbach 's proposal here #29345 (comment) looks good and works well. Instead of removing spaces, replace the 🎀 👀 🎀 |
Triggered auto assignment to @amyevans, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
hello, @abdulrahuman5196 I think my proposal is correct. please check. |
@amyevans @abdulrahuman5196 @laurenreidexpensify this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
📣 @abdulrahuman5196 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @ZhenjaHorbach 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @dhanashree-sawant 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
PR will be ready today |
Why I am not on this? |
no correct decision here. |
@Vadym-33 The proposal selection reason is already provided here #29345 (comment) When multiple proposals are similar we choose the first one. |
Not a regression. Seems to be the case for this particular currency from implementation.
No. Not beneficial for this minor bug. Seems melvin didn't udpate here automatically. But seems the issue is due for payment today - #30735 (comment) |
Payment Summary: Bug Reporter - $50 @dhanashree-sawant payment issued in Upwork |
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.3.80.0
Reproducible in staging?: y
Reproducible in production?: y
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: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696929897419459
Action Performed:
Expected Result:
Currencies should be searchable by both formats as displayed in list
Actual Result:
XOF is not searchable using it second term i.e. the text displayed after
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
android.native.XOF.not.searchable.by.second.term.mp4
Android: mWeb Chrome
android.chrome.XOF.not.searchable.by.second.term.mp4
iOS: Native
ios.native.XOF.not.searchable.by.second.term.mov
iOS: mWeb Safari
ios.safari.XOF.not.searchable.by.second.term.mov
MacOS: Chrome / Safari
Recording.4935.mp4
windows.chrome.XOF.not.searchable.by.second.term.mp4
MacOS: Desktop
mac.desktop.XOF.not.searchable.by.second.term.mov
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @laurenreidexpensifyThe text was updated successfully, but these errors were encountered: