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

changesets for branch 7.x (alpha) #5930

Merged
merged 1 commit into from
Jan 6, 2025
Merged

changesets for branch 7.x (alpha) #5930

merged 1 commit into from
Jan 6, 2025

Conversation

neo4j-team-graphql
Copy link
Collaborator

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 7.x, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

7.x is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on 7.x.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@neo4j/graphql@7.0.0-alpha.1

Major Changes

Minor Changes

  • #5868 46ab2fa Thanks @angrykoala! - Add suport for generic update operators:

    mutation {
        updateMovies(update: { name: { set: "The Matrix" } }) {
            movies {
                id
                name
            }
        }
    }
  • #5873 17911fc Thanks @MacondoExpress! - Introduce a new style for filtering relationships and connections.
    The quantifiers SOME | NONE | SINGLE | ALL are now available as a nested input object.

    Relationship

    {
        movies(where: { genres: { some: { name: { equals: "some genre" } } } }) {
            actorCount
        }
    }

    Connection

    {
        movies(where: { genresConnection: { some: { node: { name: { equals: "some genre" } } } } }) {
            actorCount
        }
    }

Patch Changes

  • #5871 722c650 Thanks @angrykoala! - Deprecate individual mutations in favor of generic mutations

    • _SET
    • _POP
    • _PUSH
    • _INCREMENT
    • _ADD
    • _DECREMENT
    • _SUBTRACT
    • _MULTIPLY
    • _DIVIDE
  • #5882 7254acf Thanks @angrykoala! - Deprecates old aggregation filters for relationships in favor of more generic filters:

    Before:

    query Movies {
      movies(
        where: { actorsAggregate: { node: { lastRating_AVERAGE_GT: 6 } } }
      ) {
        title
      }
    }

    Now:

    query Movies {
      movies(
        where: {
          actorsAggregate: { node: { lastRating: { average: { gt: 6 } } } }
        }
      ) {
        title
      }
    }
  • #5897 4f3b068 Thanks @MacondoExpress! - Deprecate relationship filtering using the non-generic version such as actors_SOME: { title_EQ: "The Matrix" } in favor of the generic input actors: { some: { title: { eq: "The Matrix" } } }.
    The setting excludeDeprecatedFields now contains the option relationshipFilters to remove these deprecated filters.

  • #5897 917482b Thanks @MacondoExpress! - Deprecate attribute filtering using the non-generic version such as title_EQ: "The Matrix" in favor of the generic input title: { eq: "The Matrix" }.
    The setting excludeDeprecatedFields now contains the option attributeFilters to remove these deprecated filters.

  • #5879 5c7ba22 Thanks @angrykoala! - Add generic filters for aggregations:

    {
        posts(where: { likesAggregate: { node: { rating: { average: { eq: 3.2 } } } } }) {
            title
        }
    }
  • #5882 7254acf Thanks @angrykoala! - Introduce the flag "aggregationFilters" to remove deprecated aggregation filters:

    const neoSchema = new Neo4jGraphQL({
        typeDefs,
        features: { excludeDeprecatedFields: { aggregationFilters: true } },
    });

@angrykoala angrykoala merged commit 3c10304 into 7.x Jan 6, 2025
37 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