-
Notifications
You must be signed in to change notification settings - Fork 842
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
Global patterns for query and filter bar #1137
Conversation
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.
Some quick reactions:
- do all the tags start with "@tags." and if so, is that detail necessary?
- I prefer the strikethrough over the circle with dash icon. Another option that might be even more clear would be text like "keyword is value" , "keyword not value". Then you could potentially do without the strikethrough and the icon.
- The full-height divider bar (and removal of the padding on pinned side of the bar) was still clearer in my personal opinion
- One last highly subjective piece of feedback :) , I want to like the neon aqua blue, but it feels a bit rich. Perhaps a more cool tone would do the trick.
It's looking great!
Thanks @ryankeairns
|
oh jeez, I now totally see that it was sample text :D |
Ok, took a peak at the current design. |
Yeah, you're probably right. How about the disabled (invisible) ones? |
In this case, the icon and gray colors feel appropriate and effective. Given the limitations of gray text and retaining accessible contrast, the icon feels like a good alternative. Additionally, limiting icon usage to this single (presumably less frequent) use case makes it stand out more without the aforementioned downside of creating too much noise. |
This is looking sweet. Agree on the icons / strikethrough feedback from @ryankeairns. I tried to take a stab at the pinning stuff. It's pretty difficult to solve. Here are some slants I went through. Prolly is the most clearEh? Eh...? Ehhhh I know it's super spacious, but it should be clear and scale ok. I know this is gonna sound silly, but it might also give us some range if we wanted to do AND/OR style grouping in a UI format. Oh, and I'd only show the actions and filter add on the row you were hovering on. Has the side benefit of letting you add stuff to the pinned set immediately. Prolly has trouble scaling with lots of items |
I also think we should keep the (x) remove button always on the filter otherwise it's really hard to quickly remove a bunch (without removing all at once). |
I like the one with no wrapping input a lot. 👍 |
Oooo, really liking these options! |
Somewhat related, had to put something together for logging that allows for highlighting separate of the query bar (think "hosts: all" and then highlight the term "error"). Right now I have it as something that appears after the KQL bar since it's an operation that happens after the filtering. I don't think they'll ever have the secondary filter bar so i don't think the two will ever be seen at once. Space is at a premium in logging, which is why it's all done in a popover. |
73aad03
to
f89f495
Compare
No longer POC, but kinda WIP |
and fixing some other layout stuff
This reverts commit 1c3ad3e.
48dafb5
to
144963f
Compare
instead of border because a border was causing the box-shadow to be off
PropTypes.shape({ | ||
asPlainText: PropTypes.bool, | ||
}), | ||
PropTypes.object, |
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.
this looks like a bad merge with master? let's keep the shape
Fix global filters position on window resize
Ok, this is ready for final (and code) review. |
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 (code review, pulled locally), added one small comment;
this looks beautiful
} | ||
|
||
componentDidMount() { | ||
// Simulate initial load. |
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.
remove if not needed
Thanks all! I'm going to merge this one in. It may develop further as @Bargs starts using it. |
This PR is no longer a WIP, but it does still have some issues that need to be worked out.
Dependent on #1139 going in firstDependent on #1173 going in firstThe main focus of the work is on the filter bar. The query bar's auto-complete can be re-used from current implementation.
The components for this pattern are contained in the docs folder, but if need be, can be moved to EUI components.
I still need to:
All that being said, this is VERY close to finished, so cc'ing @Bargs as well for initial feedback of feasibility in using this as a pattern to replace the current implementation.