-
Notifications
You must be signed in to change notification settings - Fork 909
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
Increase filters popover size and use full width in form components #352
Increase filters popover size and use full width in form components #352
Conversation
Signed-off-by: galangel <gal0angel@gmail.com>
✅ DCO Check Passed 3bfe0c3 |
I like this. |
+1 |
Hey thanks for this! Tests pass for me. Desktop experience looks great! But after talking with the team, I am worried about the mobile experience. As seen below, before and after on mobile. Even though Dashboards is intended to be a desktop experience, could there be improvements to make sure the text field isn't overflowing outside of the popover? |
For consistency, I would like to see screenshots 1, 3 and 4 have the same style rather than 4 be different for no reason. So since 1 and 3 are already the same why not make 4 the same style by adding a "Range" label above the range input and make range input full width. |
@@ -294,7 +295,6 @@ class FilterEditorUI extends Component<Props, State> { | |||
onChange={this.onFieldChange} | |||
singleSelection={{ asPlainText: true }} | |||
isClearable={false} | |||
className="globalFilterEditor__fieldInput" |
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.
If you remove this class then the change you made to #355 is not going to work?
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.
Yes, initially I used the subjects, now that I use the class, I Will revert this change in this PR
@@ -84,6 +84,7 @@ function RangeValueInputUI(props: Props) { | |||
return ( | |||
<div> | |||
<EuiFormControlLayoutDelimited | |||
fullWidth={false} |
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.
As mentioned in my other comment I don't see why this value input is going to have a different style than phrases. I think instead you should change make this full width like you did the other input fields and change the aria-label below to just a normal label.
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.
Thank you so much for taking a look!
About the full-width for the range:
I did so because, In my opinion, it wasn't looking great. I added the full-width prop so for consistency.
But sure, I will make a change and update the photo. Tell me what you think after.
About the label:
sadly that's a prop from EUI
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.
If we're trying to get the same style then you will have to use similar components. Meaning switch the EuiFormControlLayoutDelimited to EuiFormRow like the other value inputs.
@kavilla Thank you for looking at this! |
Hi @galangel -I don't think i've done a deep dive in terms of what the EUI sizes are for mobile devices. I know their 's' breakpoint is at 575px, and based on 2020 usage data, the most common min size is 375px (360px for iPhone mini, but i'm not sure that's something we want to use as a benchmark) - My sense is that below the "s" breakpoint, things should just go edge to edge and stacked. |
Signed-off-by: galangel <gal0angel@gmail.com>
❌ DCO Check Failed ac57170 |
@JacobBrandt can you re-review? I cant request in the UI =) |
@kavilla I have updated the width settings |
@galangel The DCO checks are failing. It looks like the merge commit wasn't properly signed |
❌ DCO Check Failed 69d19d0 |
@boktorbb-amzn can you help me with that? I'm not sure how to do it =) |
Hey @galangel, it looks like your new commit is signed but the DCO check fails because your older commit |
69d19d0
to
df0d7bb
Compare
✅ DCO Check Passed df0d7bb |
@boktorbb-amzn so I changed the commits, 🙏🏻 please 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.
Looks good to me. Thanks for the contribution!
Bumping =) @kavilla can you add your review so we could continue? |
@galangel Just getting back from vacation. I'll test it out tonight. |
Sorry about the delay in merging this. Would you be able to create a backport PR into https://github.com/opensearch-project/OpenSearch-Dashboards/tree/1.x? |
…ents * use full width * Update width * observer Backport PR: opensearch-project#352 Signed-off-by: galangel <gal0angel@gmail.com>
Signed-off-by: galangel gal0angel@gmail.com
Description
The change resizes the modal to 600 ( instead of 400 ) and uses the full-width prop in the form components to take advantage of the space.
also Removed the unused styles
I explicitly left the range input at false because I think it looks better like this than with full width
Fullscreen at 100%
Issues Resolved
Filters popover modal is too small
Check List