v3.6.1

Fixed issue with deployment. v3.6.0 was not published due to an issue.

v3.6.0

Added support for graphql v14.0.0

v3.5.0

Added compatibility with graphql v0.13.0

v3.4.0

• Added compatibility with graphql v0.12.0
• Fixed a bug where parsing an invalid literal value (for a Date, DateTime and Time) resulted in the value quietly being set to null without raising an error (see issue #72)

v3.3.0

Added compatibility with graphql v0.11.0

v3.2.0

Added compatibility with graphql v0.10.0, see #40 (thanks @aruberto).

v3.1.1

Bug Fix

Fixed a bug in GraphQLDate where javascript Date instances were not converted to UTC before being serialized (see #26).

v3.1.0

New

This release adds flow types in the NPM package which will help use this package in conjunction with the flow type checker.

Flow now catches errors when the package is imported wrongly:

// Flow error because import is wrong.
import { GraphQLDat } from "graphql-iso-date"

v3.0.0

Introduction of a set of date/time scalars that implement the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.

New

• Scalar Time representing a time string at UTC.
• Scalar DateTime representing a date-time string at UTC.

Improvements

• Scalar Date can now be serialized from a date string. In earlier versions this scalar could only be serialized from a javascript Date instance.

Breaking

• The Date scalar is no longer the default export. Instead, it is now a named export called GraphQLDate. In order to update from versions 2.x and below do the following:

+ import { GraphQLDate } from 'graphql-iso-date'
- import GraphQLDate from 'graphql-iso-date'

v2.1.1

Fixed a peer dependencies issue that caused conflicts when using both this library and graphql in the same project. As a result of this fix graphql versions v0.5.x up to v0.9.x are now supported. This is quite a critical bug fix, therefore it is recommended to upgrade if you haven't already.