Open zonika opened 5 years ago
I agree that we should have a consolidated input, but I'm not sure what the best implementation would be. The material design datepicker (and timepicker) are notably separate, and the native datetime-local
input has really poor browser support / UX. I think one option might be to enable NLP in a consolidated datetime-local field, similarly to how we fallback our timepicker on unsupported browsers, but that presents its own UX issues.
Could we just have a component that contains the other two components and is responsible for their combined values?
In several components, we have conditionally required date and time inputs that are combined into a timestamp on model.save. Would be great if we had an input that combines the datepicker and the timepicker inputs and creates a timestamp in kiln to save a bunch of repeated code and funky conditional require logic. This will probably prove helpful for choreographer components in the future, as well as overall simplicity of the current UI.