-
Notifications
You must be signed in to change notification settings - Fork 189
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
Fixes #1807: [UI 2.0] SearchHelp #1909
Conversation
@rjayroso I launched the vercel deployment, and after making a request saw this: |
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 except for the display error I specified above - try looking into web/src/pages/search.tsx
to solve it.
Also, it will be great if you can squash those commits when the PR is ready.
maxWidth: 500, | ||
fontSize: theme.typography.pxToRem(22.5), | ||
border: '1px solid #dadde9', | ||
subtitle: { |
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 don't see where are you using this Subtitle
- do we need it?
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.
Good catch! It's not needed anymore I'll take it out after I figure out how to work out that display error you found above
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.
Sounds good, ping me if you actually need help figuring it out
const useStyles = makeStyles((theme: Theme) => ({ | ||
container: { | ||
width: '50%', | ||
transform: 'translate(-50%, -50%)', |
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.
Why do you need to transform
?
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 isn't using the right font (Times New Roman), needs to be removed when the loading spinner starts, and when search content is shown. I'm also not a huge fan of centered text like this.
@rjayroso Rebase @izhuravlev What do you think about it? @huynguyez I think your new design will land after this PR. So I would appreciate your opinion here. I think this PR will be a temporary solution to the component. |
Sounds good to me! In the meantime, I tried my best to address the issues above.
Excuse the old search bar below, I haven't pulled the current design yet 8c4b04f80c2bfacc8ce43fbc8843cc13.mp4Let me know if I need to change anything, font colour, size, etc. |
@rjayroso I love it, looks good to me. The only thing that I thought of is that we can probably surround it with a separate "Box". What I mean is that the SearchHelp can be displayed in a rectangle of a different colour, so it is visually separated - but this smth we should ask @PedroFonsecaDEV about. |
@rjayroso Okay, I just opened the deployment and this is what I saw: After searching it removes the bottom SearchHelper, but it leaves the top one be. Also, not sure if it is related, on small resolutions like iPhone X if no results have been found only the picture is displayed - I can't scroll to the "no Results Found" Message. Try rebasing it and see if it changes anything. You might also look into the |
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.
Rebase so we can review it with the latest version of our master.
So far this looks pretty good. If we don't want to play with the logic a bit and make this being displayed only when the search page is shown for the first time - LGTM. other than that - I would play a bit with the logic here, so the SearchHelp is displayed when there are no results found as well. |
I think we can merge this and I'll file an issue to improve the SearchHelp logic |
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, Don't forget to file a new issue.
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.
Rebase this, and you can merge this in @rjayroso
Changes were made
* Removed HTML Tooltip, added className to elements * Cleaned up header imports * Removed old CSS and implemented new UI styling * Changed CSS values to better fit with planned design * Removed subtitle styling, no longer needed * Added state hook to hide visibility of SearchHelp * Redesign implemented * Rebased and put SearchHelp below SearchResults in layout
Rebased |
Issue This PR Addresses
Implements and closes #1807
Type of Change
Description
As per the new 2.0 UI Design, I have re-styled the search helper. See pictures below:
See #1804 for complete design reference. Currently, the SearchHelper component is static - I think that it should be handled within the SearchBar/SearchInput components (when the user types the help disappears). Let me know if this isn't the case cc @PedroFonsecaDEV
Checklist