Skip to content
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 toast for import #10290

Merged
merged 1 commit into from
Nov 20, 2021

Conversation

abhinandan13jan
Copy link
Contributor

@abhinandan13jan abhinandan13jan commented Oct 21, 2021

Addresses

https://issues.redhat.com/browse/ODC-6392
https://issues.redhat.com/browse/ODC-6380

Screenshot

Screenshot 2021-11-15 at 6 15 59 PM

Screenshot 2021-11-15 at 6 15 30 PM

Screenshot 2021-11-15 at 6 15 17 PM

Screenshot 2021-11-15 at 6 15 12 PM

Screenshot 2021-11-15 at 6 15 45 PM

Tests

Added test suite for importToast

Browser conformance

Chrome

@openshift-ci openshift-ci bot added component/dev-console Related to dev-console kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated labels Oct 21, 2021
@jerolimov
Copy link
Member

@abhinandan13jan Good direction, but this solution has currently some UI issues and ignores some import cases:

image

  1. I believe we should not show the link twice. Is it possible to create a link which is also copyable? Maybe it could look like this:

In ticket ODC-6380 we will need also change this in the topology sidebar. It's definitely not required to reuse this component here, but maybe you can take a look.

image

I would recommend one link with two icons. :)

This UI change would also help that the link is not rendered without any space behind the "Deployment created successfully" message.

  1. At the moment the link has also no http:// prefix. When the user clicks on the link this opens http://localhost:9000/react-web-app-3-christoph.apps-crc.testing and shows a 404 instead of her/his application.

  2. And finally, the code works currently only for Deployments. It should also work for DeploymentConfigs and Serverless Deployments. Please also notice that the Route checkbox could be unchecked by the user. So if the user creates a Deployment (or DC or Knative Service) without the Route option we should still show a notification but could not display any link in that case.

@abhinandan13jan
Copy link
Contributor Author

@jerolimov I've updated accordingly.. Can you please re-visit

@abhinandan13jan
Copy link
Contributor Author

/retest

@jerolimov
Copy link
Member

jerolimov commented Oct 27, 2021

@openshift/team-devconsole-ux @beaumorley I think we need your UX feedback here,

a) Are you fine with the toast / notification layout in the first comment?

Sorry, I personally would still suggest not to use the gray bar to show a link. We use this to copy and paste data, like ConfigMap/Secrets keys or values. Esp. we do not use such a box on the topology sidebar to show the same infos. We show there just a link.

I suggest a UI more like the sidebar:

image

Wdyt?

b) There are two strings which shows which resources are created

RESOURCE ADDED
Deployment created succeessfully.

This strings currently doesn't depend on the Deployment type we created. Should we add different cases* for that or could we use a more generic term here like "Application created successfully."? Wdyt?

*Deployment vs DeploymentConfig vs Serverless Service.

@openshift-ci openshift-ci bot added the component/core Related to console core functionality label Oct 29, 2021
@abhinandan13jan
Copy link
Contributor Author

@jerolimov Created new component to handle all the discussed cases. Updated screenshots please check

@jerolimov
Copy link
Member

/assign

@serenamarie125
Copy link
Contributor

don't think we want all CAPS here @abhinandan13jan but will let @beaumorley confirm

@serenamarie125
Copy link
Contributor

my concern with these two icons next to eachother is that the hit target is so small, people trying to copy will likely click the link frequently. @beaumorley what are your thoughts?

@abhinandan13jan
Copy link
Contributor Author

abhinandan13jan commented Nov 2, 2021

@serenamarie125 @beaumorley
Please let me know if increasing the padding space for the last copy-icon helps or what is to be done here?

Updated heading to Sentence case and handled case sensitive filesystem names
cc: @jerolimov

@abhinandan13jan abhinandan13jan force-pushed the importToast branch 2 times, most recently from b9fac03 to 2bb1c98 Compare November 8, 2021 12:14
@beaumorley
Copy link

beaumorley commented Nov 8, 2021

Hi all,
I discussed this with Serena today. PatternFly does have a copy link pattern. It is part of copy to clipboard like in the example above but I've formatted it slightly differently and included the external link.

Could you do something like this? There is an option in the PF spec for copy to clipboard in a form and the size of the field is this size.

image

@serenamarie125 what do you think?

@abhinandan13jan
Copy link
Contributor Author

abhinandan13jan commented Nov 9, 2021

@beaumorley @jerolimov I've updated the component to look similar to the CopyToClipboard component

Screenshot 2021-11-09 at 8 44 38 PM

Screenshot 2021-11-09 at 8 48 10 PM

Please note that:

  1. The icons are positioned same as that of the CopytoClipboard component of console
  2. This would apply across all areas where RouteLocation is exposed.

@beaumorley
Copy link

Looks great. Can you just add a period after "Deployment created successfully." <-- Like that.

Thank you.

@christianvogt
Copy link
Contributor

@beaumorley
This seems have gone through several iterations already. But I'd like to share my opinion. As a user I've been accustomed to knowing that blue text on websites equates to a link. I've also been accustomed to knowing that any link can be easily copied via right click.

While having a copy to clipboard button may be useful. my typical go to is still to right-click and copy link address. Furthermore this design for a link goes against the norm that links are blue. Having the https schema is also important in identifying text as a link. Especially if we're trying to convey to the user that this is their service URL.

image

@serenamarie125
Copy link
Contributor

serenamarie125 commented Nov 9, 2021

@beaumorley I see what @christianvogt is saying ... here's my 2 cents

New component pluses

  • I like the spacing of this new component much better
  • I like the feedback / tooltip on the copy icon

Concerns

  • I was concerned about the look of the code component being odd here and possibly confusing
  • I think the External Link icon would be before Copy because I think that's more frequently used
  • with this component, the URL is no longer a link, you'd have to click the icon. Maybe this is an issue because it's not consistent with how it's been displayed forever

@jerolimov
Copy link
Member

jerolimov commented Nov 9, 2021

+1 for showing a blue link, but also just my opinion! And to be fair, blue on gray doesn't look good. 😕

At the end someone needs to decide and we (as group) should agree one a UI now before Abhi updates it again and again. If we can not do here we should to that on PM/Eng/UX Sync...

¯_(ツ)_/¯

@beaumorley
Copy link

beaumorley commented Nov 9, 2021

Agree with your feedback @christianvogt . And your +1 Christoph. It was my initial reaction but then I tried to work with the requirement and PF patterns. I think we agree that blue linked text conveys that this is a link. The external icon conveys it is taking user to new place. These are exiting conventions.

The copy icon is being used unconventionally. @serenamarie125 do you want to go back to the other design and just put more space between the icons? Alternatively, we could just not add the copy link at all.

Here is the alter with more space between the icons.
image

@serenamarie125 is this what you had originally suggested?

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

10 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@abhinandan13jan
Copy link
Contributor Author

/test e2e-gcp-console

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

15 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 1a1de76 into openshift:master Nov 20, 2021
@spadgett spadgett added this to the v4.10 milestone Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality component/dev-console Related to dev-console docs-approved Signifies that Docs has signed off on this PR kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants