-
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 05-29-2024][$250] Group chat - "Make member" icon is the same as "Make admin" #41509
Comments
Triggered auto assignment to @lschurr ( |
@lschurr FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-collect - Release 1 |
ProposalPlease re-state the problem that we are trying to solve in this issue.What is the root cause of that problem?App/src/pages/ReportParticipantsPage.tsx Lines 233 to 240 in d03b4b9
We used wrong icon in What changes do you think we should make in order to solve the problem?Update to What alternative solutions did you explore? (Optional)Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Group chat - "Make member" icon is the same as "Make admin". What is the root cause of that problem?A wrong icon is used: App/src/pages/ReportParticipantsPage.tsx Lines 234 to 239 in d03b4b9
What changes do you think we should make in order to solve the problem?Use Expensicons.User when
Also, this logic is duplicated in
Then, use this at both the places. We can also add common logic for remove members option, isAtleastOneAdminSelected and isAtleastOneMemberSelected. |
Job added to Upwork: https://www.upwork.com/jobs/~016c4bdd4a97ecd36a |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 ( |
Thanks for proposals @ShridharGoel @cretadn22! @ShridharGoel the only thing differentiate your proposal from @cretadn22 is a minor refactor suggestion, unrelated to the bug which i dont find enough to discard the first proposal. So Proposal from @cretadn22 LGTM! 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @dangrous, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@ishpaul777 Don't you think the issue wouldn't have happened in the first place if a common method was being used? This refactor can help prevent such issues when more changes happen later. |
The almost same code was using correct icon at one place and incorrect at another. |
This will be very niche use for a util i dont think it really worth it to have a utility for such a small usecase having it in same component improves code readability IMO, that being said i'll let assigned engineer make final call on assignment. |
@ishpaul777 Is this waiting for me to create PR? Or what pending here? |
Yeah I think let's go with the simpler (first) solution for now. I totally understand where you're coming from, @ShridharGoel, but I agree that for readability it makes sense to stick with the format we already have. Maybe if we have more roles in the future we can rethink, but for the two we have now (and this bug) I'll assign @cretadn22! |
@ishpaul777 @dangrous I created the PR #41776 |
Group chat is in #vip-split, moving. |
Looks like the automation didn't fire but this hit prod 5/22 - so should be paid 5/29 |
Payment summary:
|
Great! Offer sent in Upwork. |
@lschurr Accepted your offer. Thanks 🙏 |
Payments have been sent in Upwork. All set to close this one out. |
No description provided.
The text was updated successfully, but these errors were encountered: