-
Notifications
You must be signed in to change notification settings - Fork 176
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
bug: clean search bar #1833
bug: clean search bar #1833
Conversation
🦋 Changeset detectedLatest commit: ba28ea1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thanks again for your contribution @ShatilKhan :) I noticed 2 things:
|
I've removed the right padding bug-clean-srch-bar-update.webm |
Hi @ShatilKhan :) All good for the right padding. However the @HichamELBSI do you know how we can fix this? |
Hey, to make it 32px, we just have to add a @ShatilKhan Please, feel free to do the update so we can merge all you modification 🙂 |
I'm on it |
Can you please check ? bug-clean-searchbar-vid-3.webm |
@ShatilKhan In order to merge the PR, you will need to generate changeset. You can run |
I've added the changesheet |
Thanks for your contribution @ShatilKhan |
Signed-off-by: ShatilKhan <[email protected]>
Signed-off-by: ShatilKhan <[email protected]>
Signed-off-by: ShatilKhan <[email protected]>
Signed-off-by: Shahriar Shatil <[email protected]>
Signed-off-by: Shahriar Shatil <[email protected]>
e467e47
to
ba28ea1
Compare
What does it do?
This PR updates the search bar component to match the design system specifications by:
Why is it needed?
As reported in issue #1832, the current search bar implementation had several visual inconsistencies:
Describe the issue you are solving.
How to test it?
bug-cleaner-search-bar.webm
Related issue(s)/PR(s)
#1832