Skip to content

Releases: thecodingmachine/graphqlite-bundle

v5.0.0

09 Nov 14:50
b7682aa
Compare
Choose a tag to compare

What's new:

Important breaking change:

Until now GraphQLite Bundle did not follow the general naming convention set by the main library. Thus following by GraphQLite Symfony Validator Bridge the root namespace has been changed from TheCodingMachine\Graphqlite\Bundle to TheCodingMachine\GraphQLite\Bundle and all occurrences of Graphqlite in the code and file names have been changed to GraphQLite.

If you're updating GraphQLite Bundle in existing project, make sure to replace Graphqlite occurrences with GraphQLite. That includes at least the following files:

  • config/bundles.php
  • config/packages/graphqlite.yaml

v4.1.4

22 Jun 08:30
3afc2ee
Compare
Choose a tag to compare

New feature:

Improvements

v4.1.3

31 May 07:05
18e26ff
Compare
Choose a tag to compare

Bugfix release:

v4.1.2

08 Dec 11:19
a14b9a0
Compare
Choose a tag to compare

Bugfix release

  • #82 Fixing detection of PHP 8 attributes in compiler pass

v4.1.1

08 Dec 08:50
c4951c3
Compare
Choose a tag to compare

Bugfix release:

  • #81 Making the bundle work if the ecodev/upload-graphql is not installed

v4.1.0

07 Dec 14:46
7f7b8fe
Compare
Choose a tag to compare

v4.0.8

08 Jun 11:03
a50e1a8
Compare
Choose a tag to compare

New feature

  • #66 Add new configuration properties : introspection, maximum_query_complexity and maximum_query_depth (@ThibBal)

Note: I'm adding this new feature to a bugfix release to keep version number in sync with the main graphqlite version number.

Bugfixes

Improvements

  • #70 #71 Upgrading code to remove deprecated features in Symfony 5 (@moufmouf)

Big thanks to everyone who contributed!

v4.0.7

11 May 13:10
de47f36
Compare
Choose a tag to compare

Dependency update:

  • Updating to PSR-HTTP bridge 2 #60
  • Updating PHPStan to 0.12 #65

v4.0.6

06 Mar 15:06
e233a3b
Compare
Choose a tag to compare

Dependency update release

v4.0.5

21 Feb 21:16
16f1bf3
Compare
Choose a tag to compare

Bugfix:

  • #54 The "me" query now consistently returns "null" for unlogged users.

Note: Beware! This could introduce a bug if your front-end code was not designed to accept "null" as a possible return type of the "me" query (even if "null" was always a possible return value).