8.0.0 🎉
#857
Replies: 1 comment 1 reply
-
|
Note: I did my best to provide a healthy release, but the amount of (also breaking) changes isn't easy to swallow at first! I did test drive the 8 cycle from day 0 also in production to find edge cases not covered in tests, but despite the necessary BC changes this has looked good so far. But again, it's possible something has slipped thus please ask any question here or report bugs via issues https://github.com/rebing/graphql-laravel/issues Thanks 🙏🏼 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
After quite some RC cycles, the next major release finally arrived!
Note: this new release contains a LOT of BREAKING CHANGES, please make sure to review the change changelog and test before you deploy!
High level changes:
Please find all the details below:
Breaking changes
Rewrite and simplify how schemas are handled
\Rebing\GraphQL\GraphQL::$schemasnow only holdsSchemas and not amixture of strings or arrays
\Rebing\GraphQL\GraphQL::schema()now only accepts a "schema name", but noad hoc
Schemaor "schema configs". To use ad hoc schemas, use\Rebing\GraphQL\GraphQL::buildSchemaFromConfig()and\Rebing\GraphQL\GraphQL::addSchema()\Rebing\GraphQL\GraphQL::queryAndReturnResult()(and thus also\Rebing\GraphQL\GraphQL::query()) does not accept ad hoc schemas via$opts['schema']anymore; it now only can reference a schema via its name.\Rebing\GraphQL\GraphQL::addSchema()now only acceptSchemaobjects,where before it would support ad hoc schemas via array configuration.
Use
\Rebing\GraphQL\GraphQL::buildSchemaFromConfig()for that now.\Rebing\GraphQL\GraphQL::getSchemaConfiguration()has been removed due tothe simplifications.
\Rebing\GraphQL\GraphQL::getNormalizedSchemaConfiguration()does notsupport ad hoc schemas anymore and only accepts the schema name.
\Rebing\GraphQL\GraphQLServiceProvider::bootSchemas()has been removed dueto the simplifications.
The following methods now take a
\Illuminate\Contracts\Config\Repositoryassecond argument:
\Rebing\GraphQL\GraphQL::__construct\Rebing\GraphQL\GraphQLServiceProvider::applySecurityRulesAs part of moving the architecture to an execution based middleware approach,
the following methods have been removed:
\Rebing\GraphQL\GraphQLController::handleAutomaticPersistQuerieshas beenreplaced by the
AutomaticPersistedQueriesMiddlewaremiddleware\Rebing\GraphQL\GraphQLController::queryContexthas beenreplaced by the
AddAuthUserContextValueMiddlewaremiddlewareIf you relied on overriding
queryContextto inject a custom context, younow need to create your own execution middleware and add to your
configuration
\Rebing\GraphQL\GraphQLController::executeQueryhas become obsolete, nodirect replacement.
Routing has been rewritten and simplified #757 / mfn
routeconfiguration key
graphql.routesIt's therefore also not possible anymore to register different routes for
queries and mutations within a schema. Each schema gets only one route
(except for the default schema, which is registered for the global prefix
route as well as under its name).
If necessary, this can be emulated with different schemas and multi-level
paths
graphql.prefix=>graphql.route.prefixgraphql.controllers=>graphql.route.controllerFurther, providing a controller action for
queryormutationis notsupported anymore.
graphql.middleware=>graphql.route.middlewaregraphql.route_group_attributes=>graphql.route.group_attributesgraphiql group prefix (default schema)
'method'argument must provide the HTTP methodverbs in uppercase like
POSTorGET,postorgetwill not work.level
routean empty array or null\Rebing\GraphQL\GraphQL::routeNameTransformerhas been removed-in their nameRemove the
\Rebing\GraphQL\GraphQLController::$appproperty #755 / mfnInjecting the application container early is incompatible when running within
an application server like laravel/octane, as it's not guaranteed that the
container received contains all the bindings. If you relied on this property
when extending the classes, invoke the container directly via
Container::getInstance().Remove deprecated
\Rebing\GraphQL\Support\Type::$inputObjectand\Rebing\GraphQL\Support\Type::$enumObjectproperties #752 / mfnInstead in your code, extend
\Rebing\GraphQL\Support\InputTypeand\Rebing\GraphQL\Support\EnumTypedirectlySupport for Lumen has been removed
Integrate laragraph/utils RequestParser #739 / mfn
The parsing of GraphQL requests is now more strict:
GETrequest, the GraphQL query has to be in the query parametersPOSTrequest, the GraphQL query needs to be in the bodyMixing of either isn't possible anymore
POSTrequestsThis is due to
RequestParserusing\GraphQL\Server\Helper::parseRequestParamswhich includes this checkFurther:
params_key)GraphQLUploadMiddlewarehas been removed (RequestParserincludes this functionality)In
\Rebing\GraphQL\GraphQL, renamed remaining instances of$paramsto$variablesAfter switching to
RequestParser, the support for changing the variable namewhat was supposed to
params_keyhas gone and thus the name isn't fitting anymore.Also, the default value for
$variableshas been changed tonullto betterfit the how
OperationParamsworks:old:
public function query(string $query, ?array $params = [], array $opts = []): arraynew:
public function query(string $query, ?array $variables = null, array $opts = []): arrayold:
public function queryAndReturnResult(string $query, ?array $params = [], array $opts = []): ExecutionResultnew:
public function queryAndReturnResult(string $query, ?array $variables = null, array $opts = []): ExecutionResult\Rebing\GraphQL\Support\ResolveInfoFieldsAndArgumentshas been removed$getSelectFieldsclosure no longer takes a depth parameterThe
$argsargument, of thehandlemethod of the execution middlewares requiresarrayas type.Added
This allows greater flexibility for enabling/disabling certain functionality
as well as bringing in new features without having to open up the library.
'graphql'as alias #768 / mfnThis avoids having to re-parse the same queries over and over again.
ValidationExceptionis now formatted the same way as aValidationError#748 / mfnChanged
config()function and preferable use the repository or the Facade otherwise #774 / mfn$argsargument, of thehandlemethod of the execution middlewares requiresarrayas type #843 / sforwardFixed
TypeNotFoundwhen an interface defined after another type where it is used #828 / kasian-sergeevRemoved
\Rebing\GraphQL\GraphQLServiceProvider::provideswas removed #769 / mfnIt's only relevant for deferred providers which ours however isn't (and can't
be made into with the current Laravel architecture).
This discussion was created from the release 8.0.0 🎉.
Beta Was this translation helpful? Give feedback.
All reactions