-
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-04-15] [$250] [SelectionList refactor] [Wave Collect] Extract checkbox design and placing outside the BaseListItem component to specific list item components. #38222
Comments
Triggered auto assignment to @Christinadobrzyn ( |
Job added to Upwork: https://www.upwork.com/jobs/~01e7cfec47d64461f0 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mkhutornyi ( |
Upwork job price has been updated to $250 |
Just to inform: I'll be able to start working on this once I've fished my other assignments in the Simplified collect project - most likely this Friday or Monday next week. |
@abzokhattab if you haven't seen already, there's already assignee and not open for proposals. |
didnt notice it thanks @mkhutornyi !! |
@shubham1206agra since @burczu is already working on some other wave collect task today and on Friday, would you fancy handling this task too given you have context? |
I will start on it today and finish by today only. |
👋 @burczu looks like there's a question for you here: #38448 (comment) |
@trjExpensify Ahh, sorry - I've missed that. Answered. |
Thanks! |
I am currently sick and have low capacity. Please reassign C+ |
I can take over as C+ |
📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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-04-15. 🎊 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:
|
Please assign me here as PR author. |
📣 @shubham1206agra 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
$250 to both @shubham1206agra and @DylanDylann |
Prepping payouts.
Upwork job is here. @shubham1206agra please accept the above offer in Upwork, thanks! |
Paid @DylanDylann based on this payment summary - #38222 (comment) Waiting for @shubham1206agra to accept the Upwork offer @DylanDylann do we need a regression test? |
@Christinadobrzyn I don't think we need a regression test for this issue because this is a refactor task |
DM'd @shubham1206agra about the upwork offer |
Awesome! Paid this out based on this payment summary - #38222 (comment) closing - let me know if I missed anything! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Coming from this issue: #35717 and discussed it on Slack.
We recently refactored the
SelectionList
component extracting list item components likeUserListItem
,RadioListItem
andTableListItem
and asking the parent component to decide which list item component should be used by theSelectionList
. There is also aBaseListItem
component used by all of these newly extracted item components that holds some common part of the code.Unfortunately this component still encapsulate how the checkbox used in the list item looks like and where it's placed, so the goal of this issue is to extract defining checkbox outside the
BaseListItem
and move this responsibility to specific list item components.Version Number:
Reproducible in staging?:
Reproducible in production?:
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:
Slack conversation:
Action Performed:
Break down in numbered steps
Expected Result:
Describe what you think should've happened
Actual Result:
Describe what actually happened
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ChristinadobrzynThe text was updated successfully, but these errors were encountered: