Mesh
On this page

@graphql-mesh/transport-neo4j

Changelog for @graphql-mesh/transport-neo4j: every release with its changes and the pull requests behind them.

0.13.1

Patch Changes

  • Updated dependencies [c7f0f3f, c7f0f3f]:
    • @graphql-mesh/types@0.107.1
    • @graphql-mesh/utils@0.107.1

0.13.0

Patch Changes

  • Updated dependencies [ab73b38, 51b15f4]:
    • @graphql-mesh/types@0.107.0
    • @graphql-mesh/utils@0.107.0

0.12.0

Patch Changes

0.11.1

Patch Changes

0.11.0

Patch Changes

  • Updated dependencies [b7def27]:
    • @graphql-mesh/types@0.105.0
    • @graphql-mesh/utils@0.105.0

0.10.40

Patch Changes

0.10.39

Patch Changes

0.10.38

Patch Changes

0.10.37

Patch Changes

0.10.36

Patch Changes

0.10.35

Patch Changes

0.10.34

Patch Changes

0.10.33

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/utils@0.104.32

0.10.32

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/utils@0.104.31

0.10.31

Patch Changes

0.10.30

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/utils@0.104.29

0.10.29

Patch Changes

0.10.28

Patch Changes

0.10.27

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/utils@0.104.26

0.10.26

Patch Changes

0.10.25

Patch Changes

  • Updated dependencies [4f81520]:
    • @graphql-mesh/types@0.104.23
    • @graphql-mesh/utils@0.104.25

0.10.24

Patch Changes

0.10.23

Patch Changes

0.10.22

Patch Changes

0.10.21

Patch Changes

0.10.20

Patch Changes

0.10.19

Patch Changes

0.10.18

Patch Changes

0.10.17

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/utils@0.104.19

0.10.16

Patch Changes

0.10.15

Patch Changes

0.10.14

Patch Changes

  • Updated dependencies [bb42d37, bb42d37]:
    • @graphql-mesh/types@0.104.16
    • @graphql-mesh/utils@0.104.16

0.10.13

Patch Changes

  • Updated dependencies [b077f20]:
    • @graphql-mesh/types@0.104.15
    • @graphql-mesh/utils@0.104.15

0.10.12

Patch Changes

  • Updated dependencies [1db3c6b]:
    • @graphql-mesh/types@0.104.14
    • @graphql-mesh/utils@0.104.14

0.10.11

Patch Changes

0.10.10

Patch Changes

  • Updated dependencies [ffec6e7]:
    • @graphql-mesh/utils@0.104.12
    • @graphql-mesh/types@0.104.12

0.10.9

Patch Changes

  • Updated dependencies [d61faf0]:
    • @graphql-mesh/utils@0.104.11
    • @graphql-mesh/types@0.104.11

0.10.8

Patch Changes

  • Updated dependencies [7852ccd, 7852ccd]:
    • @graphql-mesh/utils@0.104.10
    • @graphql-mesh/types@0.104.10

0.10.7

Patch Changes

  • Updated dependencies [0c18fe1]:
    • @graphql-mesh/types@0.104.9
    • @graphql-mesh/utils@0.104.9

0.10.6

Patch Changes

  • #8716 fb6e935 Thanks @enisdenjo! - Accept and support the upcoming and improved HivePubSub from @graphql-hive/pubsub

  • Updated dependencies [fb6e935, fb6e935, fb6e935]:

    • @graphql-mesh/types@0.104.8
    • @graphql-mesh/utils@0.104.8

0.10.5

Patch Changes

  • Updated dependencies [c37c23b]:
    • @graphql-mesh/types@0.104.7
    • @graphql-mesh/utils@0.104.7

0.10.4

Patch Changes

  • Updated dependencies [e2666bc]:
    • @graphql-mesh/utils@0.104.6
    • @graphql-mesh/types@0.104.6

0.10.3

Patch Changes

  • Updated dependencies [9d61d75]:
    • @graphql-mesh/utils@0.104.5
    • @graphql-mesh/types@0.104.5

0.10.2

Patch Changes

  • Updated dependencies [6b4c546]:
    • @graphql-mesh/types@0.104.4
    • @graphql-mesh/utils@0.104.4

0.10.1

Patch Changes

  • Updated dependencies [0af3d0c, 0af3d0c]:
    • @graphql-mesh/utils@0.104.3
    • @graphql-mesh/types@0.104.3

0.10.0

Minor Changes

  • #8598 e8f6253 Thanks @renovate! - BREAKING: Underlying @neo4j/graphql library got a major release. Please check the changelogs to see the breaking changes.

Patch Changes

0.9.2

Patch Changes

  • Updated dependencies [1b5d072]:
    • @graphql-mesh/utils@0.104.2
    • @graphql-mesh/types@0.104.2

0.9.1

Patch Changes

  • Updated dependencies [b6c083c, f416982]:
    • @graphql-mesh/utils@0.104.1
    • @graphql-mesh/types@0.104.1

0.9.0

Patch Changes

  • Updated dependencies [4528794, 4528794]:
    • @graphql-mesh/utils@0.104.0
    • @graphql-mesh/types@0.104.0

0.8.21

Patch Changes

  • Updated dependencies [903124f]:
    • @graphql-mesh/utils@0.103.21
    • @graphql-mesh/types@0.103.21

0.8.20

Patch Changes

  • Updated dependencies [3f5e0a1]:
    • @graphql-mesh/utils@0.103.20
    • @graphql-mesh/types@0.103.20

0.8.19

Patch Changes

  • Updated dependencies [d9cf1d3]:
    • @graphql-mesh/types@0.103.19
    • @graphql-mesh/utils@0.103.19

0.8.18

Patch Changes

  • Updated dependencies [ab0863b]:
    • @graphql-mesh/utils@0.103.18
    • @graphql-mesh/types@0.103.18

0.8.17

Patch Changes

  • Updated dependencies [eee582a]:
    • @graphql-mesh/utils@0.103.17
    • @graphql-mesh/types@0.103.17

0.8.16

Patch Changes

  • Updated dependencies [b44f8b7]:
    • @graphql-mesh/types@0.103.16
    • @graphql-mesh/utils@0.103.16

0.8.15

Patch Changes

  • Updated dependencies [b5c05c4]:
    • @graphql-mesh/types@0.103.15
    • @graphql-mesh/utils@0.103.15

0.8.14

Patch Changes

  • Updated dependencies [fc44a1e]:
    • @graphql-mesh/types@0.103.14
    • @graphql-mesh/utils@0.103.14

0.8.13

Patch Changes

0.8.12

Patch Changes

  • Updated dependencies [5180b06, c54e361]:
    • @graphql-mesh/utils@0.103.12
    • @graphql-mesh/types@0.103.12

0.8.11

Patch Changes

  • Updated dependencies [3fc1f3e, 4011203]:
    • @graphql-mesh/types@0.103.11
    • @graphql-mesh/utils@0.103.11

0.8.10

Patch Changes

  • Updated dependencies [b750a41]:
    • @graphql-mesh/utils@0.103.10
    • @graphql-mesh/types@0.103.10

0.8.9

Patch Changes

  • Updated dependencies [10ba2c4]:
    • @graphql-mesh/utils@0.103.9
    • @graphql-mesh/types@0.103.9

0.8.8

Patch Changes

  • Updated dependencies [93fb364]:
    • @graphql-mesh/utils@0.103.8
    • @graphql-mesh/types@0.103.8

0.8.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.103.7
    • @graphql-mesh/utils@0.103.7

0.8.6

Patch Changes

0.8.5

Patch Changes

  • Updated dependencies [9f9f6fe]:
    • @graphql-mesh/utils@0.103.5
    • @graphql-mesh/types@0.103.5

0.8.4

Patch Changes

  • Updated dependencies [8fcfe3f]:
    • @graphql-mesh/types@0.103.4
    • @graphql-mesh/utils@0.103.4

0.8.3

Patch Changes

  • Updated dependencies [6360755]:
    • @graphql-mesh/utils@0.103.3
    • @graphql-mesh/types@0.103.3

0.8.2

Patch Changes

  • Updated dependencies [bfd8929]:
    • @graphql-mesh/utils@0.103.2
    • @graphql-mesh/types@0.103.2

0.8.1

Patch Changes

0.8.0

Patch Changes

  • Updated dependencies [0e49907, 9873b33]:
    • @graphql-mesh/utils@0.103.0
    • @graphql-mesh/types@0.103.0

0.7.15

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.102.13
    • @graphql-mesh/utils@0.102.13

0.7.14

Patch Changes

  • Updated dependencies [eee53b9]:
    • @graphql-mesh/utils@0.102.12
    • @graphql-mesh/types@0.102.12
    • @graphql-mesh/transport-common@0.7.13

0.7.13

Patch Changes

0.7.12

Patch Changes

0.7.11

Patch Changes

0.7.10

Patch Changes

  • e5af4f9 Thanks @ardatan! - Fix Neo4j SSL issue

  • Updated dependencies [fad4d27]:

    • @graphql-mesh/utils@0.102.9
    • @graphql-mesh/types@0.102.9
    • @graphql-mesh/transport-common@0.7.10

0.7.9

Patch Changes

0.7.8

Patch Changes

0.7.7

Patch Changes

  • Updated dependencies [bf588d3]:
    • @graphql-mesh/utils@0.102.6
    • @graphql-mesh/types@0.102.6
    • @graphql-mesh/transport-common@0.7.7

0.7.6

Patch Changes

  • Updated dependencies [3bf14b3, b7f6ebf, 0a3e52c]:
    • @graphql-mesh/utils@0.102.5
    • @graphql-mesh/types@0.102.5
    • @graphql-mesh/transport-common@0.7.6

0.7.5

Patch Changes

  • Updated dependencies [5146df0]:
    • @graphql-mesh/transport-common@0.7.5

0.7.4

Patch Changes

0.7.3

Patch Changes

0.7.2

Patch Changes

  • Updated dependencies [5d95aad]:
    • @graphql-mesh/utils@0.102.2
    • @graphql-mesh/types@0.102.2
    • @graphql-mesh/transport-common@0.7.2

0.7.1

Patch Changes

  • Updated dependencies [e49a7e6, 60bfc22]:
    • @graphql-mesh/utils@0.102.1
    • @graphql-mesh/transport-common@0.7.1
    • @graphql-mesh/types@0.102.1

0.7.0

Patch Changes

  • Updated dependencies [db41f96]:
    • @graphql-mesh/types@0.102.0
    • @graphql-mesh/utils@0.102.0
    • @graphql-mesh/transport-common@0.7.0

0.6.2

Patch Changes

0.6.1

Patch Changes

  • #7516 67e1062 Thanks @enisdenjo! - Transport’s kind doesn’t need to be typed

  • Updated dependencies [67e1062]:

    • @graphql-mesh/transport-common@0.6.1

0.6.0

Patch Changes

0.5.0

Patch Changes

0.4.7

Patch Changes

  • Updated dependencies [a1bfc49]:
    • @graphql-mesh/types@0.99.7
    • @graphql-mesh/utils@0.99.7
    • @graphql-mesh/transport-common@0.4.7

0.4.6

Patch Changes

0.4.5

Patch Changes

  • Updated dependencies [33c23e8]:
    • @graphql-mesh/utils@0.99.5
    • @graphql-mesh/types@0.99.5
    • @graphql-mesh/transport-common@0.4.5

0.4.4

Patch Changes

  • Updated dependencies [597e790, 597e790]:
    • @graphql-mesh/utils@0.99.4
    • @graphql-mesh/types@0.99.4
    • @graphql-mesh/transport-common@0.4.4

0.4.3

Patch Changes

  • Updated dependencies [5e5dec5, 5e5dec5]:
    • @graphql-mesh/utils@0.99.3
    • @graphql-mesh/types@0.99.3
    • @graphql-mesh/transport-common@0.4.3

0.4.2

Patch Changes

0.4.1

Patch Changes

0.4.0

Patch Changes

0.3.1

Patch Changes

0.3.0

Patch Changes

  • #7145 7544594 Thanks @Author, @User! - New Federation Composition Approach for the new Mesh v1 alpha; (If you are using Mesh v0 legacy, ignore this changelog)

    Now Mesh Compose produces a superset of Federated Supergraph.

    • Drop any options and implementation related to the old fusiongraph
      • The output is a valid supergraph that can be consumed by any Federation router. But if it is not Mesh Serve, the subgraph should still be served via Mesh Serve then consumed by that Federation router. If it is Mesh Serve, no additional server is needed because Mesh Serve already knows the additional directives etc of the transports
    • Compose the subgraphs using @theguild/federation-composition package
      • So benefit from the validation rules of Federation in Mesh Compose
    • Ability to consume existing federated subgraphs
      • Since the composition is now Federation, we can accept any federated subgraph
    • Implement Federation transform to transform any subgraph to a federated subgraph by adding Federation directives (v2 only) . This is on user’s own because they add the directives manually. And for __resolveReference, we use @merge directive to mark a root field as an entity resolver for Federation
    • Use additional @source directive to consume transforms on the subgraph execution (field renames etc)
    • Use additional @resolveTo directive to consume additional stitched resolvers
    • Use additional @transport directive to choose and configure a specific transport for subgraphs
    • Handle unsupported additional directives with another set of additional directives on Query for example directives on unions, schema definitions, enum values etc and then @extraUnionDirective added with missing directives for unions then on the runtime these directives are added back to the union for the subgraph execution of the transports.

    Basically Mesh Compose uses Federation spec for composition, validation and runtime BUT the output is a superset with these additional directives imported via @composeDirective;

    • @merge (Taken from Stitching Directives) If a custom entity resolver is defined for a root field like below, the gateway will pick it up as an entity resolver;
    type Query {
   fooById(id: ID!): Foo @merge(keyField: 'id', keyArg: 'id', subgraph: Foo)
}
    • @resolveTo (Taken from v0) This allows to delegate to a field in any subgraph just like Schema Extensions in old Schema Stitching approach;
        extend type Book {

        @resolveTo(
          sourceName: "authors"
          sourceTypeName: "Query"
          sourceFieldName: "authors"
          keyField: "authorId"
          keysArg: "ids"
        )
    }
    • @source Taken from Fusion This allows us to know how the original definition is in the subgraph. If this directive exists, the runtime applies the transforms from Schema Stitching during the subgraph execution. This directive can exist in arguments, fields, types etc.
    type Query {
 @source(type: "MyUser") # This means `User` is actually `MyUser` in the actual subgraph
}

type User @source(name: "MyUser") {
  id: ID
  name: String
}
    • @transport Taken from Fusion This allows us to choose a specific transport (rest, mysql, graphql-ws, graphql-http etc) for the subgraph execution with some configuration. In the runtime, the gateway loads the transports and passes the subgraph schema with annotations if needed to get an executor to execute queries against that subgraph.
    schema @transport(subgraph: "API", kind: "rest", location: "http://0.0.0.0:<api_port>") {
  query: Query
  mutation: Mutation
  subscription: Subscription
}
    • @extraSchemaDefinitionDirective By default, it is not possible to add directives from subgraph to the supergraph but it is possible to do the same thing on types or fields. So we add this directive to Query for the directives we want to add to the schema. Then the runtime picks those per subgraph to put the directives back to their original places;
    type Query @extraSchemaDefinitionDirective(
  directives: {transport: [{subgraph: "petstore", kind: "rest", location: "http://0.0.0.0:<petstore_port>/api/v3"}]}
)  {
    • @extraEnumValueDirective and @extraTypeDirective Same for enum values and unions etc that are not supported by the composition library

    Thanks to these directives, subgraphs can be published individually to Hive for example then the supergraph stored there can be handled by Mesh Gateway since the composition is the same. All the additions etc are done on the subgraph level. For the Fed gateways except Mesh Serve, subgraphs can be served individually by Mesh Serve again while they are consumed by any gw like Apollo Router Shareable is enabled by default for non-federated subgraphs

    Documentation PR has details for users; https://github.com/ardatan/graphql-mesh/pull/7109

  • Updated dependencies [f985978, 7544594, 7544594]:

    • @graphql-mesh/utils@0.98.9
    • @graphql-mesh/transport-common@0.3.0
    • @graphql-mesh/types@0.98.9

0.2.8

Patch Changes

  • #7054 88d6232 Thanks @ardatan! - Use Disposable pattern for plugins and transports

  • Updated dependencies [4c75671, 88d6232]:

    • @graphql-mesh/types@0.98.8
    • @graphql-mesh/transport-common@0.2.8

0.2.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.98.7
    • @graphql-mesh/transport-common@0.2.7

0.2.6

Patch Changes

0.2.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/types@0.98.5
    • @graphql-mesh/transport-common@0.2.5

0.2.4

Patch Changes

  • fb59244 Thanks @ardatan! - Update GraphQL Tools packages

  • Updated dependencies [fb59244]:

    • @graphql-mesh/transport-common@0.2.4
    • @graphql-mesh/types@0.98.4

0.2.3

Patch Changes

  • c47b2aa Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [c47b2aa]:

    • @graphql-mesh/transport-common@0.2.3
    • @graphql-mesh/types@0.98.3

0.2.2

Patch Changes

  • 96dd11d Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [96dd11d]:

    • @graphql-mesh/transport-common@0.2.2
    • @graphql-mesh/types@0.98.2

0.2.1

Patch Changes

  • Updated dependencies [6044b7f]:
    • @graphql-mesh/types@0.98.1
    • @graphql-mesh/transport-common@0.2.1

0.2.0

Patch Changes

0.1.5

Patch Changes

  • Updated dependencies [52f74e7]:
    • @graphql-mesh/types@0.97.5
    • @graphql-mesh/transport-common@0.1.5

0.1.4

Patch Changes

  • Updated dependencies [ff33394]:
    • @graphql-mesh/types@0.97.4
    • @graphql-mesh/transport-common@0.1.4

0.1.3

Patch Changes

  • Updated dependencies [57f4a60]:
    • @graphql-mesh/types@0.97.3
    • @graphql-mesh/transport-common@0.1.3

0.1.2

Patch Changes

  • Updated dependencies [7a712ab]:
    • @graphql-mesh/types@0.97.2
    • @graphql-mesh/transport-common@0.1.2

0.1.1

Patch Changes

  • Updated dependencies [dbaf72c]:
    • @graphql-mesh/types@0.97.1
    • @graphql-mesh/transport-common@0.1.1

0.1.0

Patch Changes

  • Updated dependencies [92dce67]:
    • @graphql-mesh/types@0.97.0
    • @graphql-mesh/transport-common@0.1.0

0.0.2

Patch Changes

0.0.1

Patch Changes

  • #6551 7c18a3f Thanks @enisdenjo! - New Neo4J transport

  • Updated dependencies [4b3ea1d]:

    • @graphql-mesh/types@0.96.5
    • @graphql-mesh/transport-common@0.0.2