changesets for branch 4.0.0 (beta)
#3902
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to 4.0.0, this PR will be updated.
4.0.0is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exiton4.0.0.Releases
@neo4j/graphql@4.0.0-beta.3
Major Changes
#3858
92d7e251eThanks @darrellwarde! - Theoperationsargument of@subscriptionhas been renamed toevents, with each event being past tense. This mirrors naming used elsewhere for subscriptions.#3823
dd7afb97fThanks @darrellwarde! - The@iddirective has had a number of breaking changes.The
uniqueargument has been removed. In an effort to simplify directives,@idwill now only only be responsible for the autogeneration of UUID values.If you would like the property to also be backed by a unique node property constraint, use the
@uniquedirective alongside@id.The
autogenerateargument has been removed. With this value set tofalseand the above removal of constraint management, this would make the directive a no-op.The
globalargument has been removed. This quite key feature of specifying the globally unique identifier for Relay was hidden away inside the@iddirective. This functionality has been moved into its own directive,@relayId, which is used with no arguments. The use of the@relayIddirective also implies that the field will be backed by a unique node property constraint.Note, if using the
@idand@relayIddirective together on the same field, this will be an autogenerated ID compatible with Relay, and be backed by a single unique node property constraint. If you wish to give this constraint a name, use the@uniquedirective also with theconstraintNameargument.Patch Changes
8ac6d88faThanks @darrellwarde! -cypherParamsin the context now work as expected when using the OGM@neo4j/graphql-ogm@4.0.0-beta.3
Patch Changes
#3830
8ac6d88faThanks @darrellwarde! -cypherParamsin the context now work as expected when using the OGMUpdated dependencies [
92d7e251e,dd7afb97f,8ac6d88fa]:@neo4j/graphql-toolbox@2.0.5-beta.3
Patch Changes
92d7e251e,dd7afb97f,8ac6d88fa]: