Skip to content

Latest commit

 

History

History
396 lines (255 loc) · 15.1 KB

UPGRADE.md

File metadata and controls

396 lines (255 loc) · 15.1 KB
Raw

Upgrade Guide

Instructions

  1. Determine the current version (composer info ...)
  2. Choose the wanted version
  3. Follow the instructions
  4. ??????
  5. PROFIT

For example, if the current version is 2.x and you want to migrate to 5.x, you need to perform all steps in the following order:

  • "Upgrade from v2"
  • "Upgrade from v3"
  • "Upgrade from v4"

Please also see changelog to find all changes.

Legend

🤝 Backward-compatible change. Please note that despite you can ignore it now, but it will be mandatory in the future.

Tips

Tip

Maybe a good idea to add test (at least) with GraphQLAssertions::assertGraphQLSchemaEquals() assertion before the upgrade 🤗

Upgrade from v7

  • Laravel v10 is not supported anymore. Migrate to the newer version.

Upgrade from v6

General

  • PHP 8.1 is not supported anymore. Migrate to the newer version.

  • Direct usages of Container::getInstances() were replaced by explicit constructor parameters. You may need to update your code accordingly (#151).

  • Package config now uses objects instead of an array, it is recommended to migrate to the new format. 🤝

  • The JsonStringType is not implement TypeDefinition anymore. To add the scalar into the Schema, you can use @type/@scalar directive, or create a custom implementation of TypeDefinition contract to use with Builder/Manipulator.

Tests

  • Following traits required app() method to get access to the Container (#151)

    protected function app(): Application {
    return $this->app;
}

  • GraphQLAssertions methods updated to allow null for $message argument.

API

This section is actual only if you are extending the package. Please review and update (listed the most significant changes only):

Upgrade from v5

General

  • Laravel v9 is not supported anymore. Migrate to the newer version.
  • Input type auto-generation reworked and may include more/fewer fields. Please check the documentation and update the schema if needed.

@searchBy

  • enum SearchByTypeFlag { yes } => enum SearchByTypeFlag { Yes }. 🤝

  • @searchByOperators => @searchByExtendOperators. 🤝

  • @searchByOperatorRelation => @searchByOperatorRelationship (and class too; generated types will be named as SearchByRelationship* instead of SearchByComplex*). 🤝

  • 💀\LastDragon_ru\LaraASP\GraphQL\SearchBy\Operators::Condition => \LastDragon_ru\LaraASP\GraphQL\SearchBy\Operators::Object.

  • Scalars to add operators were renamed

    • SearchByCondition => SearchByOperatorsObject

    • SearchByNull => SearchByOperatorsNull

    • SearchByExtra => SearchByOperatorsExtra

    • SearchByNumber => SearchByOperatorsNumber

    • SearchByEnum => SearchByOperatorsEnum

  • Added the root type that will contain only extra operators and newly added field operator. The new query syntax is:

    query {
    # WHERE name = "LastDragon"
    users(where: {
        field: { name: {equal: "LastDragon"} }
    }) {
        id
    }
}

    If you want to use old query syntax, you need:

    1. Add following bindings into application provider:

      $this->app->bind(
    LastDragon_ru\LaraASP\GraphQL\SearchBy\Types\Condition\Root::class,
    LastDragon_ru\LaraASP\GraphQL\SearchBy\Types\Condition\V5::class,
);
$this->app->bind(
    LastDragon_ru\LaraASP\GraphQL\SearchBy\Types\Condition\Condition::class,
    LastDragon_ru\LaraASP\GraphQL\SearchBy\Types\Condition\V5::class,
);

    2. Disable SearchByOperatorFieldDirective operator to avoid possible conflict with field names (via schema or config)

      extend scalar SearchByOperatorsDisabled
@searchByOperatorField

  • If you define additional operators via scalar SearchBy* use extend scalar SearchBy* instead (or you will get TypeDefinitionAlreadyDefined error).

@sortBy

  • enum SortByTypeFlag { yes } => enum SortByTypeFlag { Yes }. 🤝

  • enum SortByTypeDirection { asc, desc } => enum SortByTypeDirection { Asc, Desc }. 🤝

  • If you are testing generated queries, you need to update sort_by_* alias to lara_asp_graphql__sort_by__*.

  • If you are overriding Extra operators, you should to add SortByOperators::Extra to use new built-in:

    extend scalar SortByOperatorsExtra
@sortByExtendOperators
@sortByOperatorRandom
    $settings = [
    'sort_by'   => [
        'operators' => [
            SortByOperators::Extra => [
                SortByOperators::Extra,
                SortByOperatorRandomDirective::class,
            ],
        ],
    ],
];

  • If you are using 💀FieldResolver, use BuilderFieldResolver instead. 🤝

  • Added the root type that will contain only extra operators and newly added field operator. The new query syntax is:

    query {
    # ORDER BY user.name ASC, text DESC
    comments(order: [
        {field: {user: {name: asc}}}
        {field: {text: desc}}
    ])
}

    If you want to use old query syntax, you need:

    1. Add following bindings into application provider:

      $this->app->bind(
    LastDragon_ru\LaraASP\GraphQL\SortBy\Types\Clause\Root::class,
    LastDragon_ru\LaraASP\GraphQL\SortBy\Types\Clause\V5::class,
);
$this->app->bind(
    LastDragon_ru\LaraASP\GraphQL\SortBy\Types\Clause\Clause::class,
    LastDragon_ru\LaraASP\GraphQL\SortBy\Types\Clause\V5::class,
);

    2. Disable SortByOperatorFieldDirective operator to avoid possible conflict with field names (via schema or config)

      extend scalar SortByOperatorsDisabled
@sortByOperatorField

  • @sortByOperatorRandom cannot be added to FIELD_DEFINITION anymore.

  • If you define addition operators via scalar SortBy* use extend scalar SortBy* instead (or you will get TypeDefinitionAlreadyDefined error).

  • Scalars to add operators were renamed

    • SortByExtra => SortByOperatorsExtra

API

This section is actual only if you are extending the package. Please review and update (listed the most significant changes only):