Skip to content

Conversation

@darrellwarde
Copy link
Contributor

No description provided.

@neo-technology-commit-status-publisher
Copy link
Collaborator

neo-technology-commit-status-publisher commented Aug 30, 2023

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

Copy link
Contributor

@Liam-Doodson Liam-Doodson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@darrellwarde darrellwarde merged commit c12ec3e into neo4j:main Aug 31, 2023
Copy link
Contributor

@lidiazuin lidiazuin left a 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
Copy link
Contributor

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?

Suggested change
=== `@exclude` removed
=== `@exclude` label:[deprecated]


=== `@exclude` removed

The `@exclude` directive has been removed in favor of much more granular configuration directives.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change


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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants