Skip to content

fix: incorrect 24 hour format comment example#15649

Merged
paulpopus merged 3 commits into
payloadcms:mainfrom
tim-at-erdee:patch-1
Apr 2, 2026
Merged

fix: incorrect 24 hour format comment example#15649
paulpopus merged 3 commits into
payloadcms:mainfrom
tim-at-erdee:patch-1

Conversation

@tim-at-erdee

Copy link
Copy Markdown
Contributor

What?

The code comment for type CollectionConfig.versions.drafts.schedulePublish.timeFormat suggests using 'hh:mm' for a 24 hour clock format. I changed this comment to instead suggest 'HH:mm'.

Why?

The lowercase 'hh' makes a 12 hour format, not the suggested 24 hour format.

How?

I replaced the comment to suggest using uppercase 'HH' instead.

-   * @example 'hh:mm' will give a 24 hour clock
+   * @example 'HH:mm' will give a 24 hour clock

The example of hh:mm still creates a 12 hour clock view, it should use HH:mm to be 24 hours.
@github-actions github-actions Bot added the stale label Mar 22, 2026
@paulpopus paulpopus enabled auto-merge (squash) April 2, 2026 17:21
@paulpopus paulpopus merged commit f42b767 into payloadcms:main Apr 2, 2026
311 of 314 checks passed
@github-actions

github-actions Bot commented Apr 8, 2026

Copy link
Copy Markdown
Contributor

🚀 This is included in version v3.82.0

milamer pushed a commit to milamer/payload that referenced this pull request Apr 20, 2026
### What?

The code comment for type
`CollectionConfig.versions.drafts.schedulePublish.timeFormat` suggests
using 'hh:mm' for a 24 hour clock format. I changed this comment to
instead suggest 'HH:mm'.

### Why?

The lowercase 'hh' makes a 12 hour format, not the suggested 24 hour
format.

### How?

I replaced the comment to suggest using uppercase 'HH' instead.

```diff
-   * @example 'hh:mm' will give a 24 hour clock
+   * @example 'HH:mm' will give a 24 hour clock
 ```

Co-authored-by: Paul Popus <paul@payloadcms.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants