-
Notifications
You must be signed in to change notification settings - Fork 15
Adds some missing migration steps, and fixes a typo #25
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
Adds some missing migration steps, and fixes a typo #25
Conversation
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Liam-Doodson
left a comment
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.
LGTM!
lidiazuin
left a comment
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.
I've seen you merged the PR while I was reviewing, so I'll just leave these comments to catch up on a new PR for an editorial review :)
|
|
||
| Additionally, escaping strings is no longer needed. | ||
|
|
||
| === `@exclude` removed |
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.
Can't we use the label deprecated for it?
| === `@exclude` removed | |
| === `@exclude` label:[deprecated] |
|
|
||
| === `@exclude` removed | ||
|
|
||
| The `@exclude` directive has been removed in favor of much more granular configuration directives. |
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 `@exclude` directive has been removed in favor of much more granular configuration directives. | |
| The `@exclude` directive has been removed in favor of a more granular configuration directives. |
| === `@exclude` removed | ||
|
|
||
| The `@exclude` directive has been removed in favor of much more granular configuration directives. | ||
|
|
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 `@exclude` directive has been removed in favor of much more granular configuration directives. | ||
|
|
||
| The new `@query`, `@mutation` and `@subscription` directives instead allow for fully granular configuration for each operation. |
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 new `@query`, `@mutation` and `@subscription` directives instead allow for fully granular configuration for each operation. | |
| The `@query`, `@mutation` and `@subscription` directives instead allow for fully granular configuration for each operation. |
| * `@exclude(operations: [READ])` and `@query(read: false, aggregate: false)`. | ||
| * `@exclude(operation: [CREATE, UPDATE, DELETE])` and `@mutation(operations: [])`. | ||
|
|
||
| Whilst there is more verbosity, the directives are significantly more powerful and extensible as the library gains features. |
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.
| Whilst there is more verbosity, the directives are significantly more powerful and extensible as the library gains features. | |
| Despite the verbosity, the directives are significantly more powerful and extensible as the library gains features. |
| === `@readonly` and `@writeonly` removed | ||
|
|
||
| The `@readonly` and `@writeonly` directives have been removed in favor of more granular configuration directives. | ||
| The new `@selectable` and `@settable` directives can be used to configure not only if fields are readable or writable, but also when they should be readable or writable. |
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 new `@selectable` and `@settable` directives can be used to configure not only if fields are readable or writable, but also when they should be readable or writable. | |
| The `@selectable` and `@settable` directives can be used to configure not only if fields are readable or writable, but also when they should be readable or writable. |
| } | ||
| ---- | ||
|
|
||
| === `@readonly` and `@writeonly` removed |
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.
Same here about the label
No description provided.