-
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 2024-12-09] [$125] Make sure the first result in most recents is highlighted when user uses CMD+K #51894
Comments
Job added to Upwork: https://www.upwork.com/jobs/~021852421610290735954 |
Current assignee @JmillsExpensify is eligible for the Bug assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Pujan92 ( |
Upwork job price has been updated to $125 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Make sure the first result in most recents is highlighted when user uses CMD+K What is the root cause of that problem?Improvement What changes do you think we should make in order to solve the problem?We should save the first chat index here
we will pass it here
Additionally: From the OP I can see that the list is not suppose to scrolled to the focused item on initial render but we have a code here that scroll to the focused index
we will disable this code by passing a new param shouldNotScrollToFocusedIndex
What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.Make sure the first result in most recents is highlighted when user uses CMD+K What is the root cause of that problem?I don't know if the above proposal states the same issue or not, but for me; the issue is the lack of adding the What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional) |
📣 @HusseinSamy! 📣
|
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
ProposalPlease re-state the problem that we are trying to solve in this issue.Make sure the first result in most recents is highlighted when user uses CMD+K What changes do you think we should make in order to solve the problem?The lack of an To ensure the first chat in the recent chats list is automatically highlighted when the search bar opens with CMD+K, we will:
const initiallyFocusedOptionKey = styledRecentReports.at(0)?.keyForList; and we will pass
initiallyFocusedOptionKey={initiallyFocusedOptionKey} What alternative solutions did you explore? (Optional)Contributor details |
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
@samranahm Your proposal will be dismissed because you did not follow the proposal template. |
Edited by proposal-police: This proposal was edited at 2024-11-04 10:01:40 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Make sure the first result in most recents is highlighted when user uses CMD+K What is the root cause of that problem?Changes request What changes do you think we should make in order to solve the problem?All proposals above not working if we reload the page and directly press CMD+K, also not working if the user remove the search term. So I propose the following: Create a new function called
Call it in useEffect
And on onSearchChange, if newUserQuery false App/src/components/Search/SearchRouter/SearchRouter.tsx Lines 307 to 309 in 0647baf
POC -1-New-Expensify.30.mp4What alternative solutions did you explore? (Optional) |
@JmillsExpensify, @Pujan92, @luacmartins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
1 similar comment
@JmillsExpensify, @Pujan92, @luacmartins Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@Pujan92 did you get a chance to look at the proposals above? |
Yes, let's please prioritize this one. It's coming up actively with our members. |
Sorry for the delay, I will review the proposals today. |
@JmillsExpensify, @Pujan92, @luacmartins, @nyomanjyotisa Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@JmillsExpensify, @Pujan92, @luacmartins, @nyomanjyotisa Eep! 4 days overdue now. Issues have feelings too... |
PR is being worked on. Hopefully up for review this week. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.69-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-12-09. 🎊 For reference, here are some details about the assignees on this issue:
|
@Pujan92 @JmillsExpensify @Pujan92 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Payment summary:
|
Contributor paid via NewDot. @Pujan92 do you mind filling out the BZ checklist and recommending a regression test? |
I think we don't need a checklist here as this is a new change and not a bug. Regression Test Proposal
|
Thanks regression test created. Please submit a request via New Expensify. Closing this issue out! |
$125 approved for @Pujan92 |
From the design doc.
cc @luacmartins
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @JmillsExpensifyThe text was updated successfully, but these errors were encountered: