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 dev #5087

Merged
merged 1 commit into from May 13, 2024
Merged

changesets for branch dev #5087

merged 1 commit into from May 13, 2024

Conversation

neo4j-team-graphql
Copy link
Collaborator

@neo4j-team-graphql neo4j-team-graphql commented May 7, 2024

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

Releases

@neo4j/graphql@5.3.6

Patch Changes

  • #5103 05d83b2 Thanks @angrykoala! - Optimise schema generation for aggregations, reducing schema generation time

  • #5085 c82f7b8 Thanks @angrykoala! - Validation warning on objects without resolver only appear under env variable DEBUG=@neo4j/graphql:graphql

  • #5104 bcc3719 Thanks @angrykoala! - Add feature option excludeDeprecatedFields to reduce the schema size by removing autogenerated fields that have been deprecated:

    Usage:

    const neoSchema = new Neo4jGraphQL({
        typeDefs,
        driver,
        features: {
            excludeDeprecatedFields: {
                bookmark: true,
                negationFilters: true,
                arrayFilters: true,
                stringAggregation: true,
                aggregationFilters: true,
            },
        },
    });

    This flag will remove the fields marked as @deprecated that have been autogenerated by the @neo4j/graphql library to reduce the schema size and hence server startup time and performance. Note that user-defined deprecated fields are not removed. Some autogenerated fields may still be generated, particularly those that do not affect schema size.

@neo4j/graphql-ogm@5.3.6

Patch Changes

@neo4j-team-graphql neo4j-team-graphql added this to Pull requests in PR Triage May 7, 2024
@neo4j-team-graphql neo4j-team-graphql force-pushed the changeset-release/dev branch 24 times, most recently from 969c7b0 to dcc40f1 Compare May 12, 2024 05:07
@angrykoala angrykoala merged commit 509fce4 into dev May 13, 2024
91 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
PR Triage
Pull requests
Development

Successfully merging this pull request may close these issues.

None yet

2 participants