Skip to content

Releases: webonyx/graphql-php

v0.12.1

23 Jun 04:40
89369fd
Compare
Choose a tag to compare
  • Fixed bug in validation rule OverlappingFieldsCanBeMerged (#292)
  • Added one more breaking change note in UPGRADE.md (#291)
  • Spec compliance: remove data entry from response on top-level error (#281)

v0.12.0

27 May 12:44
Compare
Choose a tag to compare
  • RFC: Block String (multi-line strings via triple-quote """string""")
  • GraphQL Schema SDL: Descriptions as strings (including multi-line)
  • Changed minimum required PHP version to 5.6

Improvements:

  • Allow extending GraphQL errors with additional properties
  • Fixed parsing of default values in Schema SDL
  • Handling several more cases in findBreakingChanges
  • StandardServer: expect operationName (instead of operation) in input

Big thanks to @danez for contributions in this release.

v0.11.6

17 Apr 10:49
Compare
Choose a tag to compare
  • Switched to MIT License
  • Restored noLocation option for parser
  • Several minor bugfixes and improvements

v0.11.5

12 Dec 09:04
Compare
Choose a tag to compare
  • Allow objects with __toString in IDType (see #210)

v0.11.4

28 Nov 13:28
Compare
Choose a tag to compare
  • findBreakingChanges utility (see #199)

v0.11.3

28 Nov 05:39
Compare
Choose a tag to compare
  • StandardServer: Support non pre-parsed PSR-7 request body (see #202)

v0.11.2

13 Oct 17:49
Compare
Choose a tag to compare
  • Bugfix: provide descriptions to custom scalars (see #181)

v0.11.1

22 Sep 16:20
Compare
Choose a tag to compare
  • Ability to override internal types via types option of the schema (see #174).

v0.11.0

20 Sep 12:51
Compare
Choose a tag to compare

This release brings little changes but there are two reasons why it is released as major version:

  1. To follow reference implementation versions (it matches 0.11.x series of graphql-js)
  2. It may break existing applications because scalar input coercion rules are stricter now:

    In previous versions sloppy client input could leak through with unexpected results.
    For example string "false" accidentally sent in variables was converted to boolean true
    and passed to field arguments. In the new version, such input will produce an error
    (which is a spec-compliant behavior).

Improvements:

  • Stricter input coercion (see #171)
  • Types built with BuildSchema now have reference to AST node with corresponding AST definition (in $astNode property)
  • Account for query offset for error locations (e.g. when query is stored in .graphql file)

v0.10.2

30 Aug 16:34
Compare
Choose a tag to compare
  • StandardServer improvement: do not raise an error when variables are passed as empty string (see #156)