Skip to content

Releases: alumbra/alumbra.spec

Spec Namespace (v0.1.11)

26 May 08:30
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

Switches to the now-correct namespaces for Clojure spec (clojure.spec.alpha.*). Thanks to @r0man!

Artifact Coordinates

[alumbra/spec "0.1.11"]

Canonical Operation Object Fields (v0.1.10)

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

Breaking Changes

None.

Features

Adds :type-name to a canonical operation object field spec.

Artifact Coordinates

[alumbra/spec "0.1.10"]

Argument Default Values (v0.1.9)

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

Breaking Changes

None.

Bugfixes

  • default values in the analyzed schema should have the same format as directive argument values.

Artifact Coordinates

[alumbra/spec "0.1.9"]

[BROKEN] (v0.1.8)

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

This release is broken. Do not use!

Argument Default Values

10 May 08:00
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

  • renames field :alumbra/argument-default-value in schema spec to :alumbra/default-value.

Features

  • add :alumbra/default-value to analyzed schema's ::argument spec.

Artifact Coordinates

[alumbra/spec "0.1.7"]

Operation Name & Variable Scope (v0.1.5)

11 Dec 11:49
@xsc xsc
Compare
Choose a tag to compare

Changes

  • Make:alumbra/operation-name nilable and a required key nearly everywhere it appears.
  • Split the :variable/exists validation error into :variable/name-in-operation-scope and :variable/name-in-fragment-scope.
  • Provide the given :alumbra/value in the :variable/default-value-correct validation error.

Artifact Coordinates

[alumbra/spec "0.1.5"]

Expected Type in Validation Error (v0.1.4)

10 Dec 18:26
@xsc xsc
Compare
Choose a tag to compare

This adds the expected type (an :alumbra/type-description) to the validation error map. Additionally, :value/type-nullable is removed since it can be expressed using :value/type-correct.

Artifact Coordinates

[alumbra/spec "0.1.4"]

Type Validation Errors (v0.1.3)

02 Dec 22:47
@xsc xsc
Compare
Choose a tag to compare

This release adjusts the validation error format for failed type checks. It removes :argument/type-correct and :variable/type-correct in favour of:

  • :value/type-nullable
  • :value/type-correct

Additionally, type descriptions are now exposed as :alumbra/type-description.

Artifact Coordiantes

[alumbra/spec "0.1.3"]

Variable Validation Errors (v0.1.2)

02 Dec 22:45
@xsc xsc
Compare
Choose a tag to compare

This release adjusts the following validation errors:

  • :variable/input-type
  • :variable/name-unique
  • :variable/default-value-correct
  • :variable/exists
  • :variable/must-be-used
  • :variable/type-correct

Specifically, :operation-name is no longer optional.

Artifact Coordinates

[alumbra/spec "0.1.2"]

Changes to Canonical Operation (v0.1.1)

25 Nov 11:33
@xsc xsc
Compare
Choose a tag to compare

Breaking Changes

  • canonical operation ::block maps are allowed to not have a type condition (since there can be directive-only blocks),
  • canonical operation arguments should reside on ::field, not ::field-spec.

Artifact Coordinates

[alumbra/spec "0.1.1"]