Skip to content

Releases: alumbra/alumbra

Fix Error Template Path (v0.2.6)

12 Jun 12:14
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Bugfixes

This fixes lookup of the alumbra error templates when Selmer's resource path is manually set (see #24).

Artifact Coordinates

[alumbra "0.2.6"]

Null Result Errors (v0.2.5)

17 May 15:28
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Features

Improves error messages when a non-nullable list/object field returns null.

Artifact Coordinates

[alumbra "0.2.5"]

Nullable Input Enums (v0.2.4)

17 May 15:27
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Bugfixes

Fixes NPE when supplying null as input to a nullable enum.

Artifact Coordinates

[alumbra "0.2.4"]

Nullable Variable & Value Fixes (v0.2.3)

15 May 13:10
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Bugfixes

  • nullable variables can now be omitted from the variables map (see alumbra/analyzer 0.1.15).
  • explicitly setting nullable lists/input object within another input object to null no longer throws an AssertionError (see alumbra/claro 0.1.13).

Artifact Coordinates

[alumbra "0.2.3"]

Enum Default Values + Parameters on 'nil' Literal (v0.2.2)

10 May 16:36
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Bugfixes

  • fixes handling of enum default values on field/directive arguments (see alumbra/analyzer).
  • fixes behaviour of parameterized literal nil values (see alumbra/claro).

Artifact Coordinates

[alumbra "0.2.2"]

Argument Default Values (v0.2.1)

10 May 15:50
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Features

  • GraphQL schemas can now contain non-scalar directive arguments, as well as default values (see #1).
  • Argument/directive default values are now passed correctly to resolvables/directive handlers (see #21).

Artifact Coordinates

[alumbra "0.2.1"]

Human-Readable Error Messages (v0.2.0)

01 May 15:41
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

  • GraphiQL functions have been removed (they might pop up in a separate utility project).
  • Errors in Ring responses no longer contain the "alumbra/validation-error" key, instead all relevant information is moved into "context".

Features

  • Validation errors are now formatted in a human-readable way (#10).
  • Errors now come with the affected part of the query, as well as (if available) a hint on common causes and solutions for the encountered error class.

Artifact Coordinates

[alumbra "0.2.0"]

Interface Fragment Spreads (v0.1.6)

28 Apr 15:25
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Bugfixes

  • fixes a problem with fragment spread on interface type fields (see #20).

Artifact Coordiantes

[alumbra "0.1.6"]

Performance Improvements (v0.1.5)

28 Apr 09:57
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Features

  • upgrades claro to 0.2.16, taking advantage of an improved internal tree representation,
  • upgrades alumbra/claro to 0.1.10, providing a better order-maintaining tree projection.

Artifact Coordinates

[alumbra "0.1.5"]

Error Improvements & Projection Performance (v0.1.4)

26 Apr 13:04
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

None.

Features

Bugfixes

Artifact Coordinates

[alumbra "0.1.4"]