Kevin Ansfield 7a5f15414b Fixed scheduled publishedAt validation being triggered unexpectedly ... no issue Problem: - the server stores time with second-level precision but we send milliseconds - when scheduling a post we were storing the selected publish-at time in the PublishOptions instance with non-zero milliseconds as the initial date was based on now+5mins - when we were saving after the initial schedule that millisecond-containing time was still being used resulting in a perceived time difference in our client-side and server-side validations indicating that the published_at value should be updated, but when that time was <2 mins in the future the published_at change validation was triggered resulting in errors Solution: - ensure we only set times on PublishOptions with 0 milliseconds - update client-side validations so we only trigger published_at validation when it's dirty Also fixed: - client-side validation errors were not shown on the confirm step due to a missing `.args`		2022-05-19 23:11:01 +01:00
..
admin	Fixed scheduled publishedAt validation being triggered unexpectedly	2022-05-19 23:11:01 +01:00