0.3.0

This is a breaking change only if you are using fp-ts APIs

• Breaking Change
  • upgrade to latest fp-ts v0.2 (@gcanti)

0.2.3

• Internal
  • upgrade to fp-ts v0.1 (@gcanti)

0.2.2

• New Feature
  • add partial combinator (makes optional props possible)
  • add readonly combinator (values are not frozen in production)
  • add readonlyArray combinator (values are not frozen in production)
  • add never type
• Breaking Changes
  • remove maybe combinator, can be defined in userland as

    export function maybe<RT extends t.Any>(type: RT, name?: string): t.UnionType<[RT, typeof t.null], t.TypeOf<RT> | null> {
      return t.union([type, t.null], name)
    }

• Polish
  • export pathReporterFailure function from default reporters
• Bug Fix
  • revert pruning excess properties (see #27 for context)
  • revert intersection combinator accepting only InterfaceTypes
• Experimental
  • Pattern matching / catamorphism for unions

0.1.1

• New Feature
  • add support for jsnext
  • add Integer type
• Breaking Changes
  • t.Object type. Renamed to t.Dictionary, now accepts arrays so is fully equivalent to { [key: string]: any }.
  • t.instanceOf combinator. Removed.
  • t.object combinator. Renamed to t.interface. ObjectType to InterfaceType. Excess properties are now pruned.
  • mapping combinator. Renamed to dictionary. MappingType to DictionaryType.
  • intersection combinator. Due to the new excess property pruning in t.interface now only accept InterfaceTypes.
  • API isSuccess removed, use either.isRight instead
  • API isFailure removed, use either.isLeft instead
  • API fromValidation removed

0.0.3

remove MaybeOf type alias, fix #19 (@gcanti)

0.0.2

reverse overloading definitions for unions, intersections and tuples, fix inference bug

0.0.1

Initial release