1Overview

The LocalDate scalar type represents a date without time or time zone information. It is intended for scenarios where only the calendar date matters in a local context, such as contract effective dates, publication dates, or recurring events (e.g., “New Year’s Day is January 1st”), where the specific time of day and time zone are irrelevant or managed separately.

Unlike instant-based DateTime scalars that represent a specific moment in time, LocalDate represents a calendar date that could refer to different moments depending on the time zone context applied to it. This makes it suitable for applications where only the date component is meaningful.

The scalar uses RFC 3339 format for serialization, specifically the full-date production.

2Recommended name

The recommended name for this scalar is LocalDate.

3Result spec

A LocalDate scalar must serialize to a string conforming to the RFC 3339 full-date production. This represents a calendar date in the format: YYYY-MM-DD.

The format is:

• YYYY: Four-digit year
• MM: Two-digit month (01-12)
• DD: Two-digit day (01-31, valid for the given month)

4Input spec

A LocalDate scalar accepts string values conforming to the RFC 3339 full-date production, both as GraphQL literals and as JSON input values.

The input format matches the result format and must:

• Follow the pattern YYYY-MM-DD
• Contain valid date values per RFC 3339
• Use hyphens as separators
• Use zero-padded two-digit months and days

Implementations should validate:

• Year is a valid four-digit number
• Month is between 01 and 12
• Day is valid for the given month and year (accounting for leap years)

mutation {
  createContract(effectiveDate: "2000-12-24") {
    id
  }
}

{
  "effectiveDate": "2000-12-24"
}

5References

• RFC 3339 — Date and Time on the Internet: Timestamps