graphql | TypeScript Ecosystem Directory

Bot releases are hidden (Show)

graphql - [email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

Updated dependencies [9befbb8, 980f078, a76c9c9, 6653a9e, 4fc08b6, 712d793, 3094db4, 99fc744, deed2ec]:
- @neo4j/[email protected]

graphql - [email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

Updated dependencies [9befbb8, 980f078, a76c9c9, 6653a9e, 4fc08b6, 712d793, 3094db4, 99fc744, deed2ec]:
- @neo4j/[email protected]
- @neo4j/[email protected]

graphql - [email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

Updated dependencies [9befbb8, 980f078, a76c9c9, 6653a9e, 4fc08b6, 712d793, 3094db4, 99fc744, deed2ec]:
- @neo4j/[email protected]
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Major Changes

#4675 9befbb8 Thanks @Andy2003! - change the name of the *EdgeAggregationWhereInput so it uses the name of the type defining the edge properties

#4410 a76c9c9 Thanks @angrykoala! - Change @relationshipProperties to target types instead of interfaces:

Instead of defining relationship properties in an interface, they must be defined as a type:

type Actor {
    name: String!
    actedIn: [Show!]! @relationship(type: "ACTED_IN", direction: OUT, properties: "ActedIn")
}

type ActedIn @relationshipProperties {
    screenTime: Int
}

#4441 6653a9e Thanks @a-alle! - Introduce new properties field in connection edges field for relationship properties.

Patch Changes

Updated dependencies [9befbb8, 980f078, a76c9c9, 6653a9e, 4fc08b6, 712d793, 3094db4, 99fc744, deed2ec]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Major Changes

#4410 a76c9c9 Thanks @angrykoala! - Change @relationshipProperties to target types instead of interfaces:

Instead of defining relationship properties in an interface, they must be defined as a type:

type Actor {
    name: String!
    actedIn: [Show!]! @relationship(type: "ACTED_IN", direction: OUT, properties: "ActedIn")
}

type ActedIn @relationshipProperties {
    screenTime: Int
}

#4441 6653a9e Thanks @a-alle! - Introduce new properties field in connection edges field for relationship properties.

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

Updated dependencies [9befbb8, 980f078, a76c9c9, 6653a9e, 4fc08b6, 712d793, 3094db4, 99fc744, deed2ec]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Migration guide

In order to help facilitate the version upgrade we have written a migration guide for migrating to 5.0.0

Major Changes

#4675 9befbb8 Thanks @Andy2003! - change the name of the *EdgeAggregationWhereInput so it uses the name of the type defining the edge properties
#4623 980f078 Thanks @angrykoala! - Makes aggregation types nullable, even if the original property is non-nullable.

This is because, in case of no nodes existing in the database, a null value will be returned by the aggregation

#4410 a76c9c9 Thanks @angrykoala! - Change @relationshipProperties to target types instead of interfaces:

Instead of defining relationship properties in an interface, they must be defined as a type:

type Actor {
    name: String!
    actedIn: [Show!]! @relationship(type: "ACTED_IN", direction: OUT, properties: "ActedIn")
}

type ActedIn @relationshipProperties {
    screenTime: Int
}

#4441 6653a9e Thanks @a-alle! - Introduce new properties field in connection edges field for relationship properties.
#4661 99fc744 Thanks @Andy2003! - The old *AggregateSelectionNonNullable-types and *AggregateSelectionNullable-types are now merged into *AggregateSelection-types`.
#4360 5c42f8d Thanks @angrykoala! - Remove _on filter for interfaces

Minor Changes

#4285 1bba6d186 Thanks @angrykoala! - Add support for top level aggregation operations on interfaces
#4257 b58812f8e Thanks @mjfwebb! - Added nested aggregations on interfaces

#4375 d3c6d0e Thanks @angrykoala! - Add support for logical operators on filters for interfaces:

interface Show {
    title: String!
}

type Movie implements Show {
    title: String!
}

type Series implements Show {
    title: String!
}

query actedInWhere {
    shows(where: { OR: [{ title: "Show 1" }, { title: "Show 2" }] }) {
        title
    }
}

#4409 387e455 Thanks @MacondoExpress! - Add support for typename_IN filters for interfaces:

interface Show {
    title: String!
}
type Movie implements Show {
    title: String!
}
type Series implements Show {
    title: String!
}

query actedInWhere {
    shows(where: { typename_IN: [Series] }) {
        title
    }
}

Patch Changes

#4644 4fc08b6 Thanks @MacondoExpress! - Fix a bug where type-name filters were not applied if used in a connect operation.
#4697 712d793 Thanks @MacondoExpress! - Fixed incorrect behavior when using relationship-specific filters as _SOME/_SINGLE/_NONE/_ALL when the target of the filter was an interface.
#4533 3094db4 Thanks @angrykoala! - Fix bug sorting by relationship properties on connections to an interface
#4521 deed2ec Thanks @angrykoala! - Fix subscription payload fields for interfaces

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

Updated dependencies [fab9ea9, fb62636, 38b1eae, 916c37e, b8a640e, 46c38d0, 92f653f, 7e129da]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

#4508 fab9ea9 Thanks @MacondoExpress! - Fix inconsistency described by the issue https://github.com/neo4j/graphql/issues/4536
#4509 fb62636 Thanks @Andy2003! - Fixes the missing takeover of custom directives for interfaces
#4513 38b1eae Thanks @Andy2003! - [Bugfix] Fixed a bug where the sort field for a connection of an interface is not created even though it has sortable fields
#4515 916c37e Thanks @Andy2003! - fix: #4514 augment interfaces the same way no matter if they are used as the target of a relationship or not
#4621 b8a640e Thanks @MacondoExpress! - Fixed a bug, where it was not possible to resolve interface fields for top-level cypher operations.
#4744 46c38d0 Thanks @mjfwebb! - Export the Neo4jGraphQLCallback type
#4512 92f653f Thanks @Andy2003! - Harmonize the generation of SubscriptionWhere- & Where- input-types, so they reuse the same logic
#4573 7e129da Thanks @Andy2003! - fix:#2697 fix aggregation filter for duration

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 8 months ago

Patch Changes

Updated dependencies [fab9ea9, fb62636, 38b1eae, 916c37e, b8a640e, 46c38d0, 92f653f, 7e129da]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 9 months ago

Patch Changes

Updated dependencies [2bb8f8b, d3c6d0e, 5c42f8d, 387e455, 4b97531, 66a19c5]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 9 months ago

Patch Changes

Updated dependencies [2bb8f8b, d3c6d0e, 5c42f8d, 387e455, 4b97531, 66a19c5]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 9 months ago

Patch Changes

#4449 2bb8f8b Thanks @mjfwebb! - Fix: allow non-generated mutations on timestamp fields

Before this patch, it wasn't possible to update a field with a timestamp directive even when the directive specified that only the UPDATE or CREATE operation field should be generated by the database.

#4375 d3c6d0e Thanks @angrykoala! - Add support for logical operators on filters for interfaces under the experimental flag:

interface Show {
    title: String!
}

type Movie implements Show {
    title: String!
}

type Series implements Show {
    title: String!
}

query actedInWhere {
    shows(where: { OR: [{ title: "Show 1" }, { title: "Show 2" }] }) {
        title
    }
}

#4360 5c42f8d Thanks @angrykoala! - Remove _on filter for interfaces under experimental flag

#4409 387e455 Thanks @MacondoExpress! - Add support for typename_IN filters for interfaces under the experimental flag:

interface Show {
    title: String!
}
type Movie implements Show {
    title: String!
}
type Series implements Show {
    title: String!
}

query actedInWhere {
    shows(where: { typename_IN: [Series] }) {
        title
    }
}

#4483 4b97531 Thanks @darrellwarde! - Fix authorization variable naming in create operations
#4507 66a19c5 Thanks @mjfwebb! - Fixes filtering on nested read operations

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 11 months ago

Patch Changes

Updated dependencies [226e5ed, 24728fe, c09aa9b, 7b310d6, 1bf0773]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 11 months ago

Patch Changes

Updated dependencies [226e5ed, 24728fe, c09aa9b, 7b310d6, 1bf0773]:
- @neo4j/[email protected]

graphql - @neo4j/[email protected]

Published by neo4j-team-graphql 11 months ago

Patch Changes

#4247 226e5ed Thanks @darrellwarde! - Fix issue in authorization context generation.
#4330 24728fe Thanks @angrykoala! - Update translation on fulltext to make it consistent for top level operations and phrase option
#4144 c09aa9b Thanks @darrellwarde! - Include the @subscriptionsAuthorization events argument in validation.
#4308 7b310d6 Thanks @mjfwebb! - Add filtering to interface aggregations
#4309 1bf0773 Thanks @MacondoExpress! - Fix an authorization bug present for validation rules with a predicate against a nested field and the Connection API. https://github.com/neo4j/graphql/issues/4292.