Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`date-format` used in OpenAPI Spec is not high enough resolution

Open
#178 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Start by locating the OpenAPI definition for the createdBy sorting timestamp and review its date-time schema, pattern, and example. Determine the higher-resolution timestamp representation needed for accurate ordering, then validate that the updated specification consistently accepts and documents it.

Written by the indexing model from the issue text.

Description

OpenAPI spec Prio 2

createdBy is used for sorting, but the format specified is:

    date-time:
      type: string
      description: Timestamp
      format: date-time
      pattern: "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}Z$"
      example: '2024-03-20T15:30:00Z'

This has a resolution of seconds. Multiple releases are definitely possible in a single second - so this would mean ordering is not accurate in all scenarios.

FYI @nscuro @oej

Dominant language
Shell
Stars
116
Forks
23
Avg merge
2d 11h
Merged PRs (30d)
63

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CycloneDX/transparency-exchange-api

All issues in CycloneDX/transparency-exchange-api

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.