Skip to content
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

Deprecate query direction options #5694

Merged

Conversation

MacondoExpress
Copy link
Contributor

@MacondoExpress MacondoExpress commented Oct 23, 2024

This PR deprecates DEFAULT_DIRECTED / DEFAULT_UNDIRECTED DIRECTED_ONLY / UNDIRECTED_ONLY as @relationship.queryDirection argument values. The options with the prefix DEFAULT are deprecated following the deprecation of the generated directed argument. The options with the suffix _ONLY have been changed to DIRECTED / UNDIRECTED as the suffix _ONLY.

This PR also adds warnings in case a deprecated value is used.

Less important changes:

  • The algorithm to define which direction to use was modified (getCypherDirection, getRelationshipDirection).
  • Redundant types are removed.

Copy link

changeset-bot bot commented Oct 23, 2024

🦋 Changeset detected

Latest commit: 43f6276

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@neo4j/graphql Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@MacondoExpress
Copy link
Contributor Author

I'm adding some integration test coverage, right now!

@MacondoExpress MacondoExpress merged commit 3a9ada1 into neo4j:6.x Oct 24, 2024
35 checks passed
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.

2 participants