-
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
[HOLD for payment 2024-03-20] [LOW] Enable pagination on SelectionList #36121
Comments
Triggered auto assignment to @abekkala ( |
@cristipaval reporting for duty 🖖 |
Do we have an update here, @lukemorawski ? |
@cristipaval no, sorry, had a more urgent bug fixes. I will be tackling that today |
@abekkala, @cristipaval, @lukemorawski Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I know Callstack devs are quite swamped atm, so most probably, @lukemorawski will have an update on Monday. |
@cristipaval yep, I was ooo on Friday. There are also couple of regressions I need address quickly. This ticket is next up in my queue. |
@lukemorawski can you provide an update? |
@abekkala started woking on it, but I need to resolve some complicated conflicts on another PR. I should have a PR today in the evening or tomorrow |
@abekkala @cristipaval @lukemorawski this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
thanks @lukemorawski |
👀 |
@lukemorawski is there any update on this one? |
@abekkala @cristipaval @lukemorawski this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
@lukemorawski do you still have some higher priority PRs that is putting this one off for a bit? |
Hey. Yes, but I posting one PR today and I'll be waiting for a review, so I should be able to finish this. Fingers crossed 🤞 |
@abekkala PR is open |
Great @lukemorawski ! Thanks! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.51-3 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-03-20. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
PAYMENT SUMMARY FOR MAR 20
@lukemorawski can you complete the checklist above? |
@fedirjh payment sent and contract ended - thank you! 🎉 |
no regression test needed |
Problem
As part of this issue, we refactored the old gigantic
OptionItem
component into multiple components focused on specific use cases. The refactoring has taken quite a long time, and in the meantime, pagination was added to the App to make the experience smoother on high-traffic accounts.Currently, the new component
SelectionList
doesn't have pagination, and the Search feature in high-traffic accounts doesn't offer the best experience.Solution
Let's enable pagination on the new
SelectionList
component.cc @mountiny
Issue Owner
Current Issue Owner: @cristipavalThe text was updated successfully, but these errors were encountered: