-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
fix(DialInNumber,InviteByEmailSection):Copy Button Ui #14552
Conversation
Hi, thanks for your contribution! |
I have already signed the CLA |
Jenkins please test this please |
Jenkins please test this please. |
I'm working on fixing the pr-tests, so hold on. I will restart the job once it is fixed. |
@HazemAbdo the PR looks good overall, just a small nit. You have an example for checking mount state for a class component here |
We have an example for exactly your use case for functional components :) |
@horymury I think I can rewrite this functionality using |
@HazemAbdo if you can convert |
c8fd34e
to
9e382fd
Compare
@horymury I rewrote dial_copy_functional.mp4 |
@HazemAbdo appreciate the effort in reusing the existing CopyButton, but at a second look I think that repurposing it for the two new cases complicates things a bit too much, for example the use of !important which we don't quite condone, plus the fact that in order for the copy button to be inline with the other 4 buttons there(invite by google, yahoo etc buttons) too many Also, on the DialInNumber component it changes a bit the previous design of the button. So I'd suggest you revert to the previous iteration with treating the isMounted case and with keeping the refactor of the DialInNumber as a functional component,which we are grateful you did :) It might have been a misunderstanding, in my previous message I was referring to CopyButton.web.tsx as an example for checking isMounted not suggesting to be reused, apologies for not being more specific. Thank you |
@horymury No problem at all I will do these changes and update the PR with them. I thought that these changes of CopyButton might not very straight forward and make it a little bit more complicated and change it is main use case and they might not be the best solution for our problem.Thank you for your valuable feedback. |
9e382fd
to
2f4820b
Compare
@horymury I rewrote dialIn_v3.mp4 |
react/features/invite/components/add-people-dialog/web/InviteByEmailSection.tsx
Show resolved
Hide resolved
react/features/invite/components/add-people-dialog/web/InviteByEmailSection.tsx
Outdated
Show resolved
Hide resolved
react/features/invite/components/add-people-dialog/web/DialInNumber.tsx
Outdated
Show resolved
Hide resolved
react/features/invite/components/add-people-dialog/web/DialInNumber.tsx
Outdated
Show resolved
Hide resolved
2f4820b
to
8344adc
Compare
Jenkins please test this please. |
1 similar comment
Jenkins please test this please. |
Fixed (Fix invite People copy number UI) #14551
New copy number button behavior:
New Copy Invitation button behavior:
copy_new.mp4