-
Notifications
You must be signed in to change notification settings - Fork 8.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
Advanced Settings to React/EUI #17465
Conversation
Here is how the current settings are categorized, as well as their user friendly names. Suggestions/Feedback on the categories as well as the actual categorization of settings highly wanted!!!
|
Oh man, this looks fantastic |
Woah! nice @jen-huang I'll pull down this week and play around with it. From your gif's, this looks fantastic |
💚 Build Succeeded |
This is great! 👍 👍 |
This is awesome! Thanks a lot ❤️ Just a few points I would like to discuss and hear your opinion on:
|
💚 Build Succeeded |
Pinging @elastic/kibana-visualizations @elastic/kibana-sharing @elastic/kibana-discovery to verify this separation makes sense to you |
This looks really nice. One comment about the categories is that some settings span more than one category. It would make sense to have the category be an array so settings can be part of multiple categories. For example, |
The Looks like a really nice improvement, that screen was getting pretty crazy. |
wrt. categorization. imho this remains OK for visualizations. |
Hey @jen-huang just some very minor designy suggestions. Feel free to take um or leave um. To help give the form some room, I'd go ahead and use a max-width panel with a background to match the styling we have in EUI. Should help keep it from being jammed next to the left side. On this dropdown, I'd probably keep the other sections around for selection, even if only one of them can be selected. Right now you have to clear a selection before you can select another one. You might want to set your flexItems to grow={false}, then set the cancel button to be an empty button. Should make them a little less in your face and size appropriately. |
💚 Build Succeeded |
💔 Build Failed |
Thanks for the feedback, all! PR has been updated with the following changes:
UI changes with new friendly names: |
💚 Build Succeeded |
This is awesome! When I filter down to a single category, then I reopen the selection list, I only see the one I previously selected which doesn't let me select multiple without unselecting, then reselecting once the entire list is repopulated. Also, maybe we should be alternating background colors, or adding |
@chrisronline I played around with some options for differentiating between field rows. It's really only an issue for the boolean settings, since there is a large gap between the Hopefully this makes the distinction a little clearer. It's not perfect, but since the Save/Cancel buttons pop up immediately when editing, I'm not too concerned about the user not knowing what changed. |
💚 Build Succeeded |
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.
LGTM!
Sorry, wrong PR, ignore comment |
@jen-huang I wanted to take a look to provide some feedback but am running into some issues pulling it down on a fresh version of kibana. Any reason I'd be getting these errors?
|
@alexfrancoeur I updated branch with master, that should resolve the dependency conflicts. You'll also need the corresponding x-pack-kibana branch if running x-pack: https://github.com/elastic/x-pack-kibana/pull/5089. |
7b7f16c
to
b35be1b
Compare
💔 Build Failed |
… is an array, adjust tests
💚 Build Succeeded |
Fixes #17045
Relates to #14791
This PR refactors the Management > Advanced Settings page to use React and EUI.
Table -> Form
Advanced Settings is now displayed as a page-long form, instead of a table. This was done after seeing the direction of the designs for Kibana v7.
Categories
The initial page is extremely long, separated by Categories. The search bar can be used to filter settings like before, but there is now also a Category filter - this should hopefully reduce the user's need to scroll forever to find a setting. This paves work for v7 as well, though v7 will likely use submenu navigation for categories rather than filtering. Categorization is done by adding a new property
category
to each setting. Settings without acategory
are treated asgeneral
for purposes of this display.Categories are listed alphabetically, except for General, which floats to the top.
Editing
Since all of the settings are now displayed as inline forms, there is no need to click an Edit button. Just start changing the value, and Save/Cancel actions will display next to the field. All field types support Escape to Cancel and most fields support Enter to Save (textarea and image fields do not).
JSON settings are validated. Settings can be cleared (reset back to default value) by clicking Reset below the field.
If the setting is an image and there isn't an image set, the file picker will display. If an image exists, it will be displayed with a Change link option below it. Image fields validate on max size, if there is one.