-
Notifications
You must be signed in to change notification settings - Fork 173
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
<DatePicker /> component autoComplete issue #1798
base: main
Are you sure you want to change the base?
<DatePicker /> component autoComplete issue #1798
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Hey @alexandermirzoyan thanks for your contribution. We've migrated to the DS v2 now; can you verify if you're still seeing the issue please as the PR is currently pointed at our v2 (v1 is maintained on branch /v1 and only High and Criticals are supported there right now). Cheers! |
Am I correct that DS v2 is working with Strapi's v5? |
@alexandermirzoyan yes Strapi 5 uses the latest design system v2 RC |
@alexandermirzoyan thank you for the contribution! As a final step, could you update the changeset? We use this mechanism to keep track of all changes, you can see the docs here you can see an example of how we update it |
@alexandermirzoyan if you have a second to add a changeset looks like we can merge 🚀 Let us know if anything isn't clear in the doc for adding the changeset |
What does it do?
Added
autoComplete="off"
prop to<DatePicker />
component by default.Why is it needed?
Fixes issue with browser's default behaviour.
How to test it?
Make sure that you have some suggestions from the browser and click on input tag from the
<DatePicker />
component.Related issue(s)/PR(s)
#1797