Open Platonn opened 4 years ago
Simplicity of the date-picker component (to be almost-native datepicker) is important. It would be good not to pollute it with the date<->datetime conversion logic. We could try to convert it: a) in some other date-picker component (which would be more smart: able to convert date<->datetime and show some UX message like "the time will be set midnight of your timezone") b) in budget form component (to be checked: does current generic MyCompany architecture allows for custom conversions around forms?)
In #9333 we've just implemented the suggested solution https://github.com/SAP/spartacus/issues/9333#issuecomment-714799752 for date picker.
My concerns:
Suggestion:
datetime<->date
in the date picker component, instead of in convertersNote: only the architecture step (1.) (breaking change) suggested above will enable the UX improvement (2.) that can be postponed.
To be discussed. Then to prioritize properly.