-
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
[discover] De-angularize index pattern selection #46347
[discover] De-angularize index pattern selection #46347
Conversation
💚 Build Succeeded |
💔 Build Failed |
💚 Build Succeeded |
…-23-discover-index-pattern-select
Pinging @elastic/kibana-app |
💚 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.
Looking much better. There were some little differences between this and Lens, so I've opened a design PR against this PR.
You can view/merger it here:
👉 PR → kertal#2
I realize there is more design work to be done here in the future, but the new selector heading was very closely matched to the headings below (Available, Selected). This makes some visual changes to those subheadings.
The height of the index pattern title did not match the heigh of the ComoBox which resulted in a jump, which I have fixed here. Also, the ComboBox dropdown was wider than its parent input, so I've added padding to the entire sidebar and removed it from the child elements.
Let me know if you have questions!
…index-pattern-select Discover sidebar style updates
…github.com:kertal/kibana into kertal-pr-2019-09-23-discover-index-pattern-select
@ryankeairns I actually have a PR that is soon to merge for Lens that changes this behavior to not swap the text for a combo box but instead uses the EuiSelectable in a popover. If you'd like to align these utilities, you can consider the new pattern in this PR #46350 or we can collaborate after 7.5. |
I'm aware of this changes, think we should finish both PRs separately, and then create a shared component for both, shouldn't be much effort |
Agreed! I already broke the popover itself into its own component. |
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. As discussed, we will incorporate the newer Lens-style design (using a popover instead of Combobox) in a follow-up PR.
@ryankeairns thx for the changes btw. 🙏 |
💚 Build Succeeded |
@elasticmachine merge upstream |
💚 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.
border: none; | ||
border-radius: 0; | ||
} | ||
.sidebar-item-title, |
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.
Out of scope for this PR, but we should move this css to our regular class name style at some point.
); | ||
} | ||
|
||
/** |
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.
Nice catch!
Thx you for the review and valuable hints dear @flash1293 ⚡️ . about the min width, I've already experimented with making the width customizable via drag and drop. this will be the direction to go, and then you should also have a min width. currently this part is still bootstrap/angular, but that will change soon |
* Implementation of DiscoverIndexPattern React component * Implement usage of the DiscoverIndexPattern * Adapt tests
Summary
Convert Discover's index pattern selection to EUI and adapt a new design.
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.- [ ] Documentation was added for features that require explanation or tutorialsFor maintainers
- [ ] This was checked for breaking API changes and was labeled appropriately