-
Notifications
You must be signed in to change notification settings - Fork 15
Add _NOT breaking change in the migration guide.
#194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Richard Sill <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be nice to add another example with includes for example.
|
|
||
| === The deprecated `_NOT` on `@relationship` filters are no longer supported | ||
|
|
||
| The deprecated `_NOT` filters on `@relationship` fields such as: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The deprecated `_NOT` filters on `@relationship` fields such as: | |
| The following deprecated `_NOT` filters on `@relationship` are removed and no longer supported: |
| - `actors_NOT` | ||
| - `actorsConnection_NOT` | ||
|
|
||
| Are removed from the schema and no longer supported, to achieve the same result use the `NONE` quantifier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Are removed from the schema and no longer supported, to achieve the same result use the `NONE` quantifier. | |
| To achieve the same in version 6.x of the GraphQL library, use the `NONE` quantifier. |
|
oh, too late, it's already merged i see :/ |
My bad! sorry, I saw the approval and I consider these no-blockers, approved and merge the suggestions on the other PR! |
As title.