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
Add copy link after token been sent for the user doesnt have email set up from design #19707
Conversation
add design copy link
# Conflicts: # plugins/CoreHome/vue/dist/CoreHome.umd.js # plugins/CoreHome/vue/dist/CoreHome.umd.min.js
This reverts commit bb081bd.
add link token
update tests
update xml tests
update tests
update tests
update tests
update screenshots
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few screenshots and comments for you to get it conforming to spec in slack 👍🏽
update css
remove password confirm for invite
update css
…19738) * Adding the abililty to exclude specific sites from the Vue site selector component. * Adding more time to make sure that the select is loaded before trying to search. * Changed things to filter the site on the server side. * Added a few new test cases. * Increasing amount of time for test. * Updated the omnifixture. * Fixing logic error in view. * Removed collation from omnifixture since it was causing issues. * Switching omnifixture back to 4.x-dev version. * Making just the bare essential changes to make local test fixtures build correctly. * Updating screenshot of API list. * revert OmniFixture-dump to 4.x-dev revert OmniFixture-dump to 4.x-dev Co-authored-by: Peter <peter@innocraft.com>
# Conflicts: # tests/UI/expected-screenshots/UIIntegrationTest_api_listing.png
merge 4.x and update copied success ui tests
rebase to next release
rebase to next release
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update safrai and enable copy success and copy again
@justinvelluppillai should be fixed now. |
fix Safrai showing random token
This is my first look at this PR, it does work 👍 and I'm aware there have already been a lot of points raised in the discussion above, I'll try to avoid rehashing previously covered comments. a) If I want to create a new user and send them their invite link on slack, then I'd probably end up doing this:
I did this a couple of times before I realized that the 'Resend Invite' link shown in step 3) would allow me to jump to step 7). So although I saw 'Resend Invite' link, it didn't register because I want to copy the link. I never wanted to send an invite in the first place, so wasn't intuitive. Could we either rename this to 'Copy Invite Link' or duplicate the link so we have 'Resend invite' and 'Copy invite link'? b) Once the 'copy link' button is used the buttons are disabled but it isn't obvious that they no longer work. If I accidentally copied something else into my clipboard and lost the copied link then clicking the 'Copy link' button again has no effect. Wouldn't it be better to hide the buttons altogether and/or replace them with a close button? c) Minor cosmetic: The resend invite popup box seems to have a different font size from the normal popups? The password popup font is much smaller, it looks like part of a different application. d) Minor point: It might be slightly clearer to say 'Link copied to the clipboard' rather than just 'Link copied'. e) Having to enter the password twice in the space of 10 seconds isn't great, probably beyond the scope of this PR, but maybe we note this somewhere else for improvement, since we're adding password prompts to more places in the UI and risk increasing user frustration. |
@bx80 I agree.
I guess this has come to the design question. @Javi-Ormaechea
|
We could possibly look at a system level solution - same as |
@bx80 yes it'd be good to maybe create a separate issue for that. I agree it wasn't fun getting links or sending invites during testing 👍🏽 |
update fonts and text
update wording
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've spent some time doing functional testing, apart from the multiple password entry annoyance which we can address elsewhere, it works as expected and allows an admin to get an invite link copied to the clipboard fairly quickly after creating the initial invite. I can't see any outstanding issues with the code.
I've pushed a couple of UI test screenshot updates, once the test builds complete without issues then I think this is ready to merge 👍
- Functional review done
- Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
- It's usable. Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
- Can't see any issues Security review done
- Wording review done
- Code review done
- Tests were added if useful/possible
- Updated Reviewed for breaking changes
- Updated Developer changelog updated if needed
- Documentation added if needed
- Existing documentation updated if needed
@peterhashair There is no need to recreate pull requests when you want to target another branch. You can simply change the target branch of a PR on GitHub. Also it is important to rebase your changes to the new target branch. |
@sgiehl yes, sorry. I confused myself there, after I recreate the PR, and release I can rebase the PR. Will avoid that in the future. |
Description:
Fixes: #19625
Add copy link after the token has been sent for the user who doesn't have an email set up from design.
WriteText
otherwiseexecuteCommand('copy')
, there is still a security risk inWriteText
, when failed, show the whole link.This problem needs to update docs as well.
Review