Daylight Savings Time got us thinking about how we could improve our Date and Date & Time Inputs. We set out to fix the following:
- Date & Time Inputs on web was sending data granular to seconds, even though we only allow end-users to work at the minute level. This could result in unexpected behavior where you’re relying on minute precision.
- Date Inputs would sometimes include incorrect timezone offset data that would result in unexpected behaviors, such as Date values being saved in the database as 1 day later than actually selected.
- Even if you set a Date Input component to be styled as a Date Text input, it would show as a Date & Time picker on certain screen sizes.
These changes bring more predictability to working with Dates and Date & Time properties in your Adalo apps. If you ran into any of these bugs in your apps, you’ll need to publish a new version to get these fixes.
Originally published on the Adalo changelog.