Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Vis: Default editor] EUIficate order and size controls #35134
[Vis: Default editor] EUIficate order and size controls #35134
Changes from 9 commits
55fe027
cad0e6f
c139a1b
f1ec9d7
5097e7a
81d1fe9
e539671
ed43584
e97424d
cd300f6
e2d7d54
bd98647
911dd03
e6b7787
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think that if you go the route of renaming this to explicitly state
half
then you won't need to depend on theprops.aggParam.name
and the margin can be added to a sibling CSS selector like:.visEditorAggParam--half + .visEditorAggParam--half
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.
Unfortunately the solution wouldn't work because of our current structure (both them are built through the existing interface and are wrapped into additional elements). They are not siblings and that was the main pain of positioning them both since the start.
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.
@cchaos are you OK with current implementation ?
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.
I just have a concern around using the aggParam name.
Will
props.aggParam.name
eve have a space in it like "name here"? If so you'll end up with a className list like:visEditorAggParam--inline visEditorAggParam--inline-name here
which causes.here
to be a valid class which is not good.I also still think you can change the class from
--inline
to--half
so it's easily understood that the CSS will make that field 50% wide.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.
It never can have a space in a name because we are using these names in a url string. These names should always have or camelCase style or
_
between words, likeintervalBase
,ip_range
,min_doc_count
,extended_bounds
and so on.This work has been already done in this commit
This file was deleted.