-
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-06][$500] [Simplified Collect][Members] WorkspaceMembersPage: Members list redesign #35712
Comments
@burczu can you please comment here so I can assign you to the issue? |
Triggered auto assignment to @adelekennedy ( |
Hi! I'm Bartek from Callstack - expert contributor group. I'll work on this issue so please assign me. Thank you. |
@burczu, @luacmartins, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Job added to Upwork: https://www.upwork.com/jobs/~01f11d2f24fdf84777 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha ( |
@burczu, @luacmartins, @adelekennedy, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mountiny The thing is there is no renderItem prop in SelectionList therefore it's not very extensible (also it's hard to change the styles from the outside). But I guess you mean you want a separate PR for refactor, and separate for actual members re-design? |
@burczu Correct, lets make the refactor of the Selection list so you can pass in customized "cells" in a separate PR |
I don't have strong feelings about whether or not this should be a totally new component or extend an existing one. Part of me thinks its a bit cleaner to keep it as its own component as we've seen what happens when we make design/style changes to the SelectionList and how that cascades into other places. So my OCD brain likes keeping them separate at least. Either way, probably a good discussion to bring to Slack! |
@shawnborton I think having separate component that wraps the SelectionList is a secondary problem until it's hard to adjust the SelectionList itself. |
Daily update: I've done most of the refactor of the Selection List now, but I need to test everything etc. I expect the PR to be published tomorrow. |
@burczu feel free to share drafts early to get early feedback too |
The PR is now published and ready for review. |
…efactor #35712 selection list refactor
The PR with members list is now ready for review: #37074 |
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. |
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. |
Payment Summary
BugZero Checklist (@adelekennedy)
|
@getusha sent you an offer for the role! |
accepted @adelekennedy |
ended contract and remitted payment |
Implement
WorkspaceMembersPage: Members list redesign
from the Simplified Collect: Profile, Members, Categories design docIssue Owner
Current Issue Owner: @burczuUpwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: