Skip to content

Studio converts date-only frontmatter to ISO and triggers conflicts even with z.string().date() #303

@Joehoel

Description

@Joehoel

Environment

  • OS: macOS (darwin)
  • Node: 22.22.0
  • Nuxt: 4.3.0
  • @nuxt/content: 3.11.0
  • nuxt-studio: 1.1.1

Reproduction

  1. Use a collection with schema:
    publishDate: z.string().date()
  2. Have content frontmatter with date-only values:
    publishDate: 2025-06-22
  3. Deploy site.
  4. Open /admin and log into Nuxt Studio.
  5. Studio shows conflict and loads publishDate as 2025-06-22T00:00:00.000Z.
  6. Clearing drafts/cookies and re-login still shows ISO conversion.

Expected

Date-only frontmatter stays as YYYY-MM-DD, and no conflict is triggered.

Actual

Studio (or the content DB it loads) rewrites date-only fields as ISO (T00:00:00.000Z), causing a persistent conflict.

Related

Possibly related to #133 (date conversion) and #251 (conflict/mismatch).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions