You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I select a time such as 12:00:00 then it ends up setting "random" milliseconds in the date value too (I get for example 2024-04-29T10:00:00.613Z, note the extra 613 milliseconds). (These are probably not random but a leftover of the number of milliseconds at the current system time.)
Unspecified date/time parts should be set to zero.
To Reproduce
Create a date field as shown above. Set a time. Observe the non-zero milliseconds in the actual field value.
Payload Version
2.14.2
Adapters and Plugins
db-mongodb, bundler-webpack
The text was updated successfully, but these errors were encountered:
Link to reproduction
No response
Describe the Bug
I have a date field set to show the time with a precision up to seconds, using settings such as:
When I select a time such as 12:00:00 then it ends up setting "random" milliseconds in the date value too (I get for example
2024-04-29T10:00:00.613Z
, note the extra 613 milliseconds). (These are probably not random but a leftover of the number of milliseconds at the current system time.)Unspecified date/time parts should be set to zero.
To Reproduce
Create a date field as shown above. Set a time. Observe the non-zero milliseconds in the actual field value.
Payload Version
2.14.2
Adapters and Plugins
db-mongodb, bundler-webpack
The text was updated successfully, but these errors were encountered: