absinthe
absinthe
v1.7.5

View Source Changelog

1-7-4

 1.7.4

  • Feature: Support Dataloader 2.0

1-7-4-1

 1.7.4

1-7-3

 1.7.3

1-7-2

 1.7.2

1-7-1

 1.7.1

1-7-0

 1.7.0

1-6-7-retired

 1.6.7 (Retired)

Originally included the items from 1.7.0, but the spec validation fix was considered too impactful for a patch release.

1-6-6

 1.6.6

1-6-5

 1.6.5

1-6-4

 1.6.4

1-6-3

 1.6.3

1-6-2

 1.6.2

1-6-1

 1.6.1

1-6-0

 1.6.0

1-5-5

 1.5.5

1-5-4

 1.5.4

1-5-3

 1.5.3

  • Bug Fix: Handle null propagation with non_null(list_of(non_null(type))) properly
  • Bug Fix: Fix double escaping issue with string literal arguments.

1-5-2

 1.5.2

  • Bug Fix: Fix issue with persistent term backend.

1-5-1

 1.5.1

  • Bug Fix: Enable hydrating resolve_type on unions. #938
  • Bug Fix: #922

v1-5-0-rc

 v1.5.0 (Rc)

  • Breaking Bug Fix: Variable types must align exactly with the argument type. Previously Absinthe allowed variables of different types to be used by accident as long as the data parsed.
  • Feature (Experimental): :persistent_term based schema backend
  • Breaking Change: telemetry event keys changed since the beta release.

v1-5-0-beta

 v1.5.0 (Beta)

  • Feature: SDL directives, other improvements
  • Feature: Output rendered SDL for a schema
  • Feature: Substantially lower subscription memory usage.
  • Documentation: Testing guide, numerous fixes and updates
  • Breaking Change: Scalar outputs are now type checked and will raise exceptions if the result tries to send the wrong data type in the result.
  • Breaking Change: telemetry event names changed from the alpha to match an emerging naming convention for tracing.
  • Breaking Change: Added phase to check validity of field names according to GraphQL spec. Might break existing schema's. Remove the Absinthe.Phase.Schema.Validation.NamesMustBeValid from the schema pipeline if you want to ignore this.
  • Breaking Change: To match the GraphQL spec, we no longer add a non-null error when a resolver on a non-null field explicitly returns its own error.
  • Breaking Change: Removed Absinthe.Traversal module

v1-5-0-alpha

 v1.5.0 (Alpha)

Alpha 0 note: 1.5.0 alpha is safe to use on existing schemas. However, there are no schema validations at the moment, so when writing new ones you may get undefined behaviour if you write an invalid schema.

v1-4

 v1.4

For changes pre-v1.5 see the v1.4 branch.