We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
marmelab
Learn more about funding links in repositories.
Report abuse
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
What you were expecting: DateTimeInput components to work correctly as list filter components
What happened instead: Month and date/time values do not register properly when values change, and often reset entirely while picker is active.
Steps to reproduce: Add a DateTimeInput as a Filter component, then try to use the date picker to select a value.
Related code: https://codesandbox.io/s/cool-sound-pdlsh4 Check the published_at filter on the Posts list view.
Environment
The text was updated successfully, but these errors were encountered:
Reproduced. Thanks for the report!
Sorry, something went wrong.
I don't think this is a bug. The problem is that you are trying to filter a date value with a date-time filter
UPDATE: No, with the correct configuration of DateField with showTime={true} and a DateTimeInput filter, I still get the problem
DateField
showTime={true}
DateTimeInput
UPDATE 2: Getting closer, the problem is the default parse function, If I remove it, it stops misbehaving
parse
Successfully merging a pull request may close this issue.
What you were expecting:
DateTimeInput components to work correctly as list filter components
What happened instead:
Month and date/time values do not register properly when values change, and often reset entirely while picker is active.
Steps to reproduce:
Add a DateTimeInput as a Filter component, then try to use the date picker to select a value.
Related code:
https://codesandbox.io/s/cool-sound-pdlsh4 Check the published_at filter on the Posts list view.
Environment
The text was updated successfully, but these errors were encountered: