Skip to content

Consistent add storage links #1823

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

Merged
merged 1 commit into from
Jul 20, 2017

Conversation

spadgett
Copy link
Member

  • Use "Add Storage" instead of "Add Storage to ..." for deployment
    configs to be consistent with other pages and other actions like edit
    health checks and set resource limits
  • Show the name of the object being edited on the add storage and add
    config files forms to be consistent with other editors

Feedback from @ncameronbritt. Let me know if you agree with these changes.

@spadgett spadgett requested a review from jwforres July 11, 2017 16:17
@spadgett
Copy link
Member Author

openshift web console 2017-07-11 12-17-52

openshift web console 2017-07-11 12-18-10

@@ -33,7 +33,7 @@ <h2 class="text-center">No config maps or secrets.</h2>
</div>

<div ng-if="configMaps.length || secrets.length || ('configmaps' | canI : 'create') || ('secrets' | canI : 'create')" class="mar-top-xl">
<h1>Add Config Files</h1>
<h1>Add Config Files: {{name}}</h1>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually not sure I like this, which editors were we doing this already?

@ncameronbritt
Copy link

I don't have a really strong opinion about "Add Storage" vs. "Add Storage to..." The question I was asking in my review was, is that overly pedantic?

With binding we do call out the thing you're creating the binding for. Not sure about the other editors. Again, no really strong opinion about adding the {{name}}.

The drastic change of context is a bigger usability concern, imho. But I also recognize that it's not something with a quick and easy fix.

@spadgett
Copy link
Member Author

I don't have a really strong opinion about "Add Storage" vs. "Add Storage to..." The question I was asking in my review was, is that overly pedantic?

That's fair. I guess my point is we don't do that for other actions that work on the deployment config (edit health checks, edit limits, add autoscaler).

@spadgett
Copy link
Member Author

@jwforres

actually not sure I like this, which editors were we doing this already?

Add storage is the only page where we don't have the name somewhere in the header.

@ncameronbritt Inconsistent breadcrumbs from the header in most of these :/

openshift web console 2017-07-11 14-31-00

openshift web console 2017-07-11 14-32-31

Different header text in these, but they have the name.

openshift web console 2017-07-11 14-32-57

openshift web console 2017-07-11 14-33-52

@spadgett
Copy link
Member Author

openshift web console 2017-07-11 14-56-43

@spadgett
Copy link
Member Author

The drastic change of context is a bigger usability concern, imho. But I also recognize that it's not something with a quick and easy fix.

Right. Trying to get some band aid fixes in until we can make the bigger changes.

@spadgett
Copy link
Member Author

So circling back on this: what should we do? I don't have a strong opinion except I'd like the editor to make it more obvious what resource you are editing. Right now the add storage page doesn't say except in the breadcrumbs, which is easy to miss.

@jwforres
Copy link
Member

"Add storage to mariadb" would make more sense to me but I'm not strongly opposed to what you have already.

@spadgett
Copy link
Member Author

I updated it to Add Storage to <name>

@jwforres
Copy link
Member

LGTM but looks like dist needs updating

@jwforres
Copy link
Member

actually looks like the spec tests bombed

@spadgett
Copy link
Member Author

Looks like it might be a flake?

@openshift openshift deleted a comment from jwforres Jul 20, 2017
@spadgett
Copy link
Member Author

Removing merge tag until I can rebase.

- Use "Add Storage" instead of "Add Storage to ..." for deployment
  configs to be consistent with other pages and other actions like edit
  health checks and set resource limits
- Show the name of the object being edited on the add storage and add
  config files forms to be consistent with other editors
@spadgett
Copy link
Member Author

[merge][severity: bug]

@openshift-bot
Copy link

Evaluated for origin web console merge up to e5c6af9

@openshift-bot
Copy link

openshift-bot commented Jul 20, 2017

Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin_web_console/34/) (Base Commit: 6faa37f) (PR Branch Commit: e5c6af9) (Extended Tests: bug)

@openshift-bot openshift-bot merged commit 296c13c into openshift:master Jul 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants