Youshido Php GraphQL Versions Save

• fix some README badges
• add a more robust implementation for TypeService::getPropertyValue()
• fix PhpStorm inspection performance complaints
• fix a bug that prevented using null as a default value
• add support for error extensions
• throw ConfigurationException when trying to add two types with the same name to the schema
• add a getImplementations() method to AbstractInterfaceType, can be used to properly discover all possible types during introspection
• run Travis CI on PHP 7.2 and 7.3 too
• run phpstan static analysis (level 1 only) during Travis CI builds
• rename the Tests directory to tests for consistency with other projects
• remove some obsolete documentation

Bug Fixes:

https://github.com/Youshido/GraphQL/issues/148 GraphQL error when providing a default value for variables https://github.com/Youshido/GraphQL/issues/144 GraphQL error when not passing value for optional variables https://github.com/Youshido/GraphQL/issues/147 DateTime/Enum types doesn't show invalid input data

Despite being a minor update this version might require you to change a few things in your code.

1. DateTimeType and DateTimeTzType types are now working properly and parsing your input string into the \DateTime object in PHP. Also you can specify the exact format of the DateType when creating a field in constructor (for examplenew DateTimeType("m/d/Y H:ia")) .
2. EnumType now can return null values as it is in the official JS library and properly use name and value if they are not equal (e.g. {value: 1, name: "ACTIVE"}
3. All scalar types consider null values as valid values

This release doesn't break backward compatibility.

Completely revamped Processor, which now has the proper behaviour for nested structure including:

• Fragments on Unions and Interfaces
• NonNullable in different configurations, e.g. NonNull of List of NonNullable and so on
• Invalid queries like { user { name { } } } are now throwing proper errors
• Optional arguments now work correctly (but don't forget to list them with a null value, otherwise you will get an error according to the graphql spec)
• __typanme on new NonNullType(new ObjectType()) now returns the correct name

All closed issues are covered with relevant unit tests.

Important Notice Enum default value has to be set using the value, not the name part.

So the proper use would be:

'status' => [
    'type' => new EnumType([
        'name'   => 'Statue',
        'values' => [
            [
                'name'  => 'ACTIVE',
                'value' => 1
            ],
            [
                'name'  => 'DELETED',
                'value' => 2
            ]
        ]
    ]),
    'defaultValue' => 1
],

Current version brings relay support, 99% test coverage, improved Schema structure and performance improvement.

All changes are described in the Changelog-1.1. You can also look at Upgrade-1.1 to see how you can quickly update your current codebase.

Refactored documentation

This version has updated documentation and slightly updated examples with InputObjectType. No major changes were introduced in this release.

Stable version with documentation