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

fix(deps): update dependency @graphql-mesh/utils to v0.98.10 #741

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-mesh/utils (source) 0.13.0 -> 0.98.10 age adoption passing confidence

Release Notes

ardatan/graphql-mesh (@​graphql-mesh/utils)

v0.98.10

Compare Source

Patch Changes

v0.98.9

Compare Source

Patch Changes
  • #​7155
    f985978
    Thanks @​ardatan! - Construct Logger during Mesh init

  • #​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 @&#8203;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 @&#8203;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 []:

v0.98.8

Compare Source

Patch Changes

v0.98.7

Compare Source

Patch Changes

v0.98.6

Compare Source

Patch Changes

v0.98.5

Compare Source

Patch Changes

v0.98.4

Compare Source

Patch Changes

v0.98.3

Compare Source

Patch Changes

v0.98.2

Compare Source

Patch Changes

v0.98.1

Compare Source

Patch Changes

v0.98.0

Compare Source

Minor Changes
Patch Changes

v0.97.5

Compare Source

Patch Changes

v0.97.4

Compare Source

Patch Changes

v0.97.3

Compare Source

Patch Changes

v0.97.2

Compare Source

Patch Changes

v0.97.1

Compare Source

Patch Changes

v0.97.0

Compare Source

Minor Changes
Patch Changes

v0.96.6

Compare Source

Patch Changes

v0.96.5

Compare Source

Patch Changes

v0.96.4

Compare Source

Patch Changes

v0.96.3

Compare Source

Patch Changes

v0.96.2

Compare Source

Patch Changes

v0.96.1

Compare Source

Patch Changes

v0.96.0

Compare Source

Patch Changes

v0.95.8

Compare Source

Patch Changes

v0.95.7

Compare Source

Patch Changes

v0.95.6

Compare Source

Patch Changes

v0.95.5

Compare Source

Patch Changes

v0.95.4

Compare Source

Patch Changes

v0.95.3

Compare Source

Patch Changes

v0.95.2

Compare Source

Patch Changes

v0.95.1

Compare Source

Patch Changes

v0.95.0

Compare Source

Patch Changes

v0.94.6

Compare Source

Patch Changes

v0.94.5

Compare Source

Patch Changes

v0.94.4

Compare Source

Patch Changes

v0.94.3

Compare Source

Patch Changes

v0.94.2

Compare Source

Patch Changes

v0.94.1

Compare Source

Patch Changes

v0.94.0

Compare Source

Minor Changes
Patch Changes

v0.93.2

Compare Source

Patch Changes

v0.93.1

Compare Source

Patch Changes

v0.43.23

Compare Source

Patch Changes

v0.43.22

Compare Source

Patch Changes

v0.43.21

Compare Source

Patch Changes

v0.43.20

Compare Source

Patch Changes

v0.43.19

Compare Source

Patch Changes

v0.43.18

Compare Source

Patch Changes

v0.43.17

Compare Source

Patch Changes

v0.43.15

Compare Source

Patch Changes

v0.43.14

Compare Source

Patch Changes

v0.43.13

Compare Source

Patch Changes

v0.43.12

Compare Source

Patch Changes

v0.43.11

Compare Source

Patch Changes

v0.43.10

Compare Source

Patch Changes

v0.43.9

Compare Source

Patch Changes

v0.43.8

Compare Source

Patch Changes

v0.43.7

Compare Source

Patch Changes

v0.43.6

Compare Source

Patch Changes

v0.43.5

Compare Source

Patch Changes

v0.43.4

Compare Source

Patch Changes

v0.43.3

Compare Source

Patch Changes

v0.43.2

[Compare Source](https://togithub.com/ardatan/graphql-mesh/compare/@graphql-mesh/[email protected]...@graphql-mesh/uti


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from e100d17 to e6e7c97 Compare February 28, 2024 17:01
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.96.6 fix(deps): update dependency @graphql-mesh/utils to v0.97.0 Feb 28, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from e6e7c97 to fa698b4 Compare March 13, 2024 20:34
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.97.0 fix(deps): update dependency @graphql-mesh/utils to v0.97.3 Mar 13, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from fa698b4 to df9717f Compare March 14, 2024 15:09
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.97.3 fix(deps): update dependency @graphql-mesh/utils to v0.97.4 Mar 14, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from df9717f to a9df069 Compare March 22, 2024 17:47
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.97.4 fix(deps): update dependency @graphql-mesh/utils to v0.97.5 Mar 22, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from a9df069 to a1a2017 Compare April 28, 2024 21:00
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.97.5 fix(deps): update dependency @graphql-mesh/utils to v0.98.0 Apr 28, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from a1a2017 to e46bfed Compare April 29, 2024 11:54
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.0 fix(deps): update dependency @graphql-mesh/utils to v0.98.1 Apr 29, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from e46bfed to 073f074 Compare April 29, 2024 14:33
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.1 fix(deps): update dependency @graphql-mesh/utils to v0.98.2 Apr 29, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from 073f074 to 3f4c441 Compare April 30, 2024 19:21
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.2 fix(deps): update dependency @graphql-mesh/utils to v0.98.3 Apr 30, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from 3f4c441 to cac58ec Compare May 8, 2024 15:04
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.3 fix(deps): update dependency @graphql-mesh/utils to v0.98.4 May 8, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from cac58ec to 7e73018 Compare May 22, 2024 12:14
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.4 fix(deps): update dependency @graphql-mesh/utils to v0.98.5 May 22, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from 7e73018 to d17ac55 Compare May 27, 2024 13:02
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.5 fix(deps): update dependency @graphql-mesh/utils to v0.98.6 May 27, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from d17ac55 to 7e13c38 Compare June 9, 2024 09:01
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.6 fix(deps): update dependency @graphql-mesh/utils to v0.98.7 Jun 9, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from 7e13c38 to a261311 Compare June 20, 2024 17:27
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.7 fix(deps): update dependency @graphql-mesh/utils to v0.98.8 Jun 20, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from a261311 to a5816b1 Compare June 26, 2024 16:50
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.8 fix(deps): update dependency @graphql-mesh/utils to v0.98.9 Jun 26, 2024
@renovate renovate bot force-pushed the renovate/graphql-mesh-utils-0.x branch from a5816b1 to 7308e05 Compare July 4, 2024 23:41
@renovate renovate bot changed the title fix(deps): update dependency @graphql-mesh/utils to v0.98.9 fix(deps): update dependency @graphql-mesh/utils to v0.98.10 Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants