Releases: graphpql/graphpinator
Releases · graphpql/graphpinator
🎉 1.0 🎉
After extremely long time in release candidates (30 RCs) and after many delays, here comes guaranteed stable version of GraPHPinator. I am aware that it took very long to get out of RC phase, but I always found something worth improving and wanted to be sure that 1.X will stay mainline for a long time.
There are still some improvements planned, but none should break compatibility with existing systems & modules.
Changes to RC 30:
- Fixed some rare & wierd bug with internal array pointer in Finalizer
- Fixed interface contract in operation location directives (return type changed to void)
1.0 rc30
1.0 rc29-2
- Fixed bug with typesystem directives having omitted arguments
1.0 rc29
- Correctly implemented Input value coercion rules
- Input field can be omitted in request and its value is then also omitted in value object (previously null was automatically added).
- This rule should probably apply to argument set (specs are not clear in this case), but this behavior is intentionally NOT implemented.
- If you wish to keep previous behavior, set default value null to all nullable fields.
1.0 rc28
- Changes in the typesystem namespace structure
- Moved all typesystem elements into
Typesystemnamespace - Merged
Type\DefnitionandTypesystem\TypeintoTypesystem\Constraint\Type ⚠️ This is a huge BC break (I promise its the last one), its the last thing to wanted to clear out before a stable release. I included aliases to avoid as many BC breaks as possible, but everyone is encouraged to refactor the namespaces to new and stable version (also, from my observations, class aliases behave unexpectedly in some situations).- Removed
\Graphpinator\Directive\FieldDirectiveResult, the constants are now located in\Graphpinator\Typesystem\Location\FieldLocation.
- Moved all typesystem elements into
1.0 rc27
1.0 rc26
- Implemented List input coercion
- Overlooked section in the specs, specifying that single value is automatically converted to list of size 1
- Because of upgrade in Parser (version 1.1), keywords are now allowed to be valid names
- Pre 1.1 Parser resolved
null/true/false/query/mutation/subscription/onas keywords and not as a valid names for fields and other entities - Whether is it valid or not is discussed in the GraphQL specification issue
- Pre 1.1 Parser resolved
1.0 rc25
1.0 rc24
1.0 rc23-2
- Fixed errors in middleware hook for variable definition