-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
React Carbon - Controlled DatePicker type='range', first input shows both values #4803
Comments
Hi 👋 we used to have a similar issue, but it's been fixed. That said, what version of Carbon are you using? If you think you are using latest Carbon, would you want to create a reduced case based on https://codesandbox.io/s/github/carbon-design-system/carbon/tree/master/packages/react/examples/codesandbox? Thanks! |
@asudoh sure, here you go: https://codesandbox.io/s/codesandbox-oliyt. Using the latest on my own code base as well: 7.7.4 |
This change adds a logic to re-format dates in `<input>` when Flatpickr's `setDate()` API is called. Flatpickr's range plugin has a similar logic to do that, but runs only if the second argument is `true`. Fixes carbon-design-system#4803.
This change adds a logic to re-format dates in `<input>` when Flatpickr's `setDate()` API is called. Flatpickr's range plugin has a similar logic to do that, but runs only if the second argument is `true`. Fixes carbon-design-system#4803.
This change adds a logic to re-format dates in `<input>` when Flatpickr's `setDate()` API is called. Flatpickr's range plugin has a similar logic to do that, but runs only if the second argument is `true`. Fixes #4803.
…esign-system#4814) This change adds a logic to re-format dates in `<input>` when Flatpickr's `setDate()` API is called. Flatpickr's range plugin has a similar logic to do that, but runs only if the second argument is `true`. Fixes carbon-design-system#4803.
…esign-system#4814) This change adds a logic to re-format dates in `<input>` when Flatpickr's `setDate()` API is called. Flatpickr's range plugin has a similar logic to do that, but runs only if the second argument is `true`. Fixes carbon-design-system#4803.
What package(s) are you using?
carbon-components-react
Summary
I'm working on setting up a date range for a table filter. I seem to get the input data okay, but when I update the form state to have the array of the two dates, and that passes back to the DatePicker component, the first DatePickerInput shows both values.
Relevant information
Our component for integrating formik with the date picker
The text was updated successfully, but these errors were encountered: