This commit is contained in:
2019-03-06 00:55:18 +00:00
parent d922b90908
commit a60f46335f

View File

@@ -15,15 +15,10 @@ TODO CLIENT STUFF
TODO NEXT
DATETIME
- DONE Wrap the date picker to work with our dates without losing time.
- DONE Wrap a time picker to work with our dates without losing the date.
- Once this is done then combine them into a single component that:
-wraps both pickers as buttons to trigger selection on either side of a text that displays read only the locale formatted dt
- single read only text field with initial display of date and time in users's locale format
- A button to the left with a calendar icon to trigger a date picker to adjust the date
- A button to the right with a clock icon to trigger a time picker to set the time
- Must validate and report validation errors just like the built in fields do
- Test on mobile and desktop and then if all is well we can move on to the other field types
- Test UTC vs local. Dates are coming in as UTC, should they display as local or UTC??
- It is already an option to set the local time zone so the conversion should be done based on the users time zone offset both coming in and going out
- When done can make a widget with the correct date and time shown locally as per users time zone offset and will be sent to server as UTC
- Test on mobile and desktop all browsers before moving on, it must be solid with error handling (required, after before etc) and etc and then if all is well we can move on to the other field types
DON'T code the user options with the currency symbol etc until after it's all been worked out client side. Use static values instad in locale.