On this page

@graphql-mesh/types

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

0.107.1

Patch Changes

  • #9650 c7f0f3f Thanks @ardatan! - gRPC: pass channelOptions through to the gRPC client

    Use this for message size limits, keepalive, and other channel args. Options are stored as entries so dotted keys like grpc.max_receive_message_length stay GraphQL-safe in the composed schema.

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import loadGrpcSubgraph from '@omnigraph/grpc'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadGrpcSubgraph('MyGrpcApi', {
            endpoint: 'localhost:50051',
            channelOptions: {
              'grpc.max_receive_message_length': 10_000_000,
              'grpc.keepalive_time_ms': 10_000,
              'grpc.keepalive_timeout_ms': 5_000,
              'grpc.keepalive_permit_without_calls': 1
            }
          })
        }
      ]
    })

    Legacy Mesh:

    sources:
      - name: MyGrpcApi
        handler:
          grpc:
            endpoint: localhost:50051
            channelOptions:
              grpc.max_receive_message_length: 10000000
              grpc.keepalive_time_ms: 10000
  • #9650 c7f0f3f Thanks @ardatan! - gRPC: add reflectionMetadata for server-reflection requests

    Send routing / auth metadata only when loading the schema via gRPC reflection (no source). Runtime RPC metadata remains metaData; HTTP headers for a remote .graphql SDL remain schemaHeaders.

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import loadGrpcSubgraph from '@omnigraph/grpc'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadGrpcSubgraph('MyGrpcApi', {
            endpoint: 'localhost:50051',
            // No `source` → schema loaded via reflection
            reflectionMetadata: {
              'grpc-service': 'proto.MyGrpcService',
              authorization: 'Bearer {env.REFLECTION_TOKEN}'
            }
          })
        }
      ]
    })

    Legacy Mesh:

    sources:
      - name: MyGrpcApi
        handler:
          grpc:
            endpoint: localhost:50051
            reflectionMetadata:
              grpc-service: proto.MyGrpcService
              authorization: 'Bearer {env.REFLECTION_TOKEN}'

0.107.0

Minor Changes

  • #9627 51b15f4 Thanks @copilot-swe-agent! - feat: serve GraphiQL offline via serve.playground.offline

    Air-gapped setups can bundle GraphiQL assets inline instead of loading them from a CDN:

    serve:
      playground:
        offline: true

    playground: true / false is unchanged. Generated artifacts import @graphql-yoga/render-graphiql when offline mode is enabled.

Patch Changes

  • #9631 ab73b38 Thanks @ardatan! - Do not silently fall back to CDN GraphiQL when serve.playground.offline is set without renderGraphiQL, and document that @graphql-yoga/render-graphiql must be installed in the app.

0.106.0

Minor Changes

  • #9609 07c7b8e Thanks @ardatan! - Batched @resolveTo joins can now match results to keys by a field on each result (valueKeyField), instead of assuming the upstream returns one row per key in request order. Use this for collection-style sources (Strapi filters, Hasura where, SQL IN (...), and similar) that return rows in their own order, skip missing keys, or return multiple rows per key.

    Example:

    extend type SearchResult {
      products: [Product!]!
        @resolveTo(
          sourceName: "Products"
          sourceTypeName: "Query"
          sourceFieldName: "productsBySkus"
          keyField: "sku"
          keysArg: "skus"
          valueKeyField: "sku"
        )
    }

    Docs: Schema Extensions → Matching results by a field (valueKeyField)

0.105.1

Patch Changes

0.105.0

Minor Changes

  • #9441 b7def27 Thanks @enisdenjo! - AWS IAM authentication for Redis cache

    IAM auth for ElastiCache/MemoryDB works by generating a short-lived SigV4 presigned URL (valid up to 15 minutes) and using it as the Redis AUTH password. The token is signed against the elasticache (or memorydb) service using the ambient AWS credentials resolved via the standard credential chain (env vars, ~/.aws/credentials, EC2 instance role, ECS task role, etc.).

    The @smithy/signature-v4 and @aws-sdk/credential-providers packages are dynamically imported only when iamAuth is configured, so gateways not using IAM auth pay zero cost.

    Usage

    Install the optional peer dependencies:

    yarn add @aws-crypto/sha256-js @aws-sdk/credential-providers @aws-sdk/util-format-url @smithy/protocol-http @smithy/signature-v4
    import RedisCache from '@graphql-mesh/cache-redis'
    
    const cache = new RedisCache({
      host: 'my-cluster.abc123.0001.use1.cache.amazonaws.com',
      port: '6379',
      username: 'iam-user-01',
      tls: true,
      iamAuth: {
        // AWS region where the cluster is deployed
        region: 'us-east-1',
        // cluster name used as the host in the SigV4 presigned URL
        clusterName: 'my-cluster',
        // IAM-enabled Redis username - must match the ElastiCache/MemoryDB user id exactly
        userId: 'iam-user-01',
        // AWS service to sign for - 'elasticache' (default) or 'memorydb'
        serviceName: 'elasticache',
        // token expiry in seconds - maximum 900 (15 minutes), defaults to 900
        tokenExpirySeconds: 900
      }
    })

    https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/auth-iam.html

0.104.30

Patch Changes

0.104.29

Patch Changes

0.104.28

Patch Changes

0.104.27

Patch Changes

0.104.26

Patch Changes

0.104.25

Patch Changes

0.104.24

Patch Changes

0.104.23

Patch Changes

  • #9283 4f81520 Thanks @dependabot! - BREAKING: experimental__persistedDocuments is now renamed to persistedDocuments

0.104.22

Patch Changes

0.104.21

Patch Changes

0.104.20

Patch Changes

0.104.19

Patch Changes

0.104.18

Patch Changes

0.104.17

Patch Changes

0.104.16

Patch Changes

0.104.15

Patch Changes

  • #8793 b077f20 Thanks @ardatan! - Support polling in an interval by milliseconds

    plugins:
      - liveQuery:
          invalidations:
            - pollingInterval: 10000 # Polling interval in milliseconds
              invalidate:
                - Query.products
  • Updated dependencies []:

    • @graphql-mesh/store@0.104.15

0.104.14

Patch Changes

  • 1db3c6b Thanks @ardatan! - Fix the behavior matching the documentation

    Now custom property accepts a factory function or the value directly. Previously it was just the path to the module with the export (./module.ts#exportName)

  • Updated dependencies []:

    • @graphql-mesh/store@0.104.14

0.104.13

Patch Changes

0.104.12

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.12

0.104.11

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.11

0.104.10

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.10

0.104.9

Patch Changes

  • #8733 0c18fe1 Thanks @ardatan! - Support Type Merging within additional type defs for subscriptions

    This allows subscription events to resolve fields from other subgraphs.

    For example, if you have a products subgraph like this:

    type Query {
      hello: String!
    }
    type Product @key(fields: "id") {
      id: ID!
      name: String!
      price: Float!
    }

    we need add the subscription fields like this:

    import { defineConfig, loadGraphQLHTTPSubgraph } from '@graphql-mesh/compose-cli'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadGraphQLHTTPSubgraph('products', {
            endpoint: `http://localhost:3000/graphql`
          })
        }
      ],
      additionalTypeDefs: /* GraphQL */ `
        extend schema {
          subscription: Subscription
        }
        type Subscription {
          newProduct: Product! @resolveTo(pubsubTopic: "new_product", sourceName: "products")
        }
      `
    })

    you can subscribe to Hive Gateway like this:

    subscription {
      newProduct {
        name
        price
      }
    }

    emit an event to the Redis instance on the new_product topic this:

    PUBLISH new_product '{"id":"roomba70x"}'

    The subscriber will then receive the following event:

    {
      "data": {
        "newProduct": {
          "name": "Roomba 70x",
          "price": 279.99
        }
      }
    }

    Because Hive Gateway merged the Product type from the products subgraph into the root schema, it can resolve the name and price fields even though they are not defined in the additionalTypeDefs.

  • Updated dependencies []:

    • @graphql-mesh/store@0.104.9

0.104.8

Patch Changes

0.104.7

Patch Changes

  • c37c23b Thanks @ardatan! - Fix filterBy expression handling

  • Updated dependencies []:

    • @graphql-mesh/store@0.104.7

0.104.6

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.6

0.104.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.5

0.104.4

Patch Changes

  • #8651 6b4c546 Thanks @ardatan! - Redis Cluster support

  • Updated dependencies []:

    • @graphql-mesh/store@0.104.4

0.104.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.3

0.104.2

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.2

0.104.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.1

0.104.0

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.104.0

0.103.21

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.21

0.103.20

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.20

0.103.19

Patch Changes

  • #8414 d9cf1d3 Thanks @ardatan! - Auto detection of SOAP version to decide SOAP namespace; For SOAP 1.1, it is set to http://schemas.xmlsoap.org/soap/envelope/ and for SOAP 1.2, it is set to http://www.w3.org/2003/05/soap-envelope.

    If you want to use a custom namespace, you can set it like below;

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import { loadSOAPSubgraph } from '@omnigraph/soap'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadSOAPSubgraph('CountryInfo', {
            source:
              'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
            soapNamespace: 'http://foo.com/schemas/soap/envelope'
          })
        }
      ]
    })
  • Updated dependencies []:

    • @graphql-mesh/store@0.103.19

0.103.18

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.18

0.103.17

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.17

0.103.16

Patch Changes

  • #8375 b44f8b7 Thanks @ardatan! - More clear key-value pairs in the logs

  • Updated dependencies []:

    • @graphql-mesh/store@0.103.16

0.103.15

Patch Changes

  • b5c05c4 Thanks @ardatan! - Export again accidentially removed RedisConfig

  • Updated dependencies []:

    • @graphql-mesh/store@0.103.15

0.103.14

Patch Changes

0.103.13

Patch Changes

0.103.12

Patch Changes

  • #8289 c54e361 Thanks @ardatan! - New option selectQueryOrMutationField to decide which field belongs to which root type explicitly.

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import loadGrpcSubgraph from '@omnigraph/grpc'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadGrpcSubgraph('MyGrpcApi', {
            /** .. **/
    
            // Prefix to collect Query method default: list, get
            prefixQueryMethod: ['list', 'get'],
    
            // Select certain fields as Query or Mutation
            // This overrides `prefixQueryMethod`
            selectQueryOrMutationField: [
              {
                // You can use a pattern matching with *
                fieldName: '*RetrieveMovies',
                type: 'Query'
              },
              // Or you can use a specific field name
              // This will make the field GetMovie available as a Mutation
              // Because it would be Query because of `prefixQueryMethod`
              {
                fieldName: 'GetMovie',
                type: 'Mutation'
              }
            ]
          })
        }
      ]
    })
  • Updated dependencies []:

    • @graphql-mesh/store@0.103.12

0.103.11

Patch Changes

  • #8196 3fc1f3e Thanks @ardatan! - - You can now choose the name of the alias you want to use for SOAP body;

    import { defineConfig } from '@graphql-mesh/compose-cli'
    
    export const composeConfig = defineConfig({
      sources: [
        {
          sourceHandler: loadSOAPSubgraph('CountryInfo', {
            source:
              'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
            bodyAlias: 'my-body'
          })
        }
      ]
    })
    • Then it will generate a body like below by using the alias;
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:my-body="http://foo.com/">
       <soap:Body>
          <my-body:Foo>
              <my-body:Bar>baz</my-body:Bar>
          </my-body:Foo>
       </soap:Body>
    </soap:Envelope>

    If you want to add SOAP headers to the request body like below;

    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:header="http://foo.com/">
       <soap:Header>
          <header:MyHeader>
             <header:UserName>user</header:UserName>
             <header:Password>password</header:Password>
          </header:MyHeader>
       </soap:Header>

    You can add the headers to the configuration like below;

    import { defineConfig } from '@graphql-mesh/compose-cli'
    import { loadSOAPSubgraph } from '@omnigraph/soap'
    
    export const composeConfig = defineConfig({
      subgraphs: [
        {
          sourceHandler: loadSOAPSubgraph('CountryInfo', {
            source:
              'http://webservices.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL',
            soapHeaders: {
              alias: 'header',
              namespace: 'http://foo.com',
              headers: {
                MyHeader: {
                  UserName: 'user',
                  Password: 'password'
                }
              }
            }
          })
        }
      ]
    })
  • Updated dependencies []:

    • @graphql-mesh/store@0.103.11

0.103.10

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.10

0.103.9

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.9

0.103.8

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.8

0.103.7

Patch Changes

  • Updated dependencies [c2349ef, e82d900]:
    • @graphql-mesh/store@0.103.7

0.103.6

Patch Changes

0.103.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.5

0.103.4

Patch Changes

  • 8fcfe3f Thanks @ardatan! - Fix compatibility between MeshPlugin and GatewayPlugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.103.4

0.103.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.3

0.103.2

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.2

0.103.1

Patch Changes

0.103.0

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.103.0

0.102.13

Patch Changes

  • Updated dependencies [fcf18fb]:
    • @graphql-mesh/store@0.102.13

0.102.12

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.12

0.102.11

Patch Changes

0.102.10

Patch Changes

0.102.9

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.9

0.102.8

Patch Changes

0.102.7

Patch Changes

0.102.6

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.6

0.102.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.5

0.102.4

Patch Changes

0.102.3

Patch Changes

0.102.2

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.2

0.102.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.1

0.102.0

Minor Changes

  • #7530 db41f96 Thanks @enisdenjo! - Support Hive’s experimental persisted documents

    import { useMeshHive } from '@graphql-mesh/plugin-hive'
    
    // Usage Reporting
    useMeshHive({
      token: '<hive_registry_token>'
    })
    
    // Persisted Documents
    useMeshHive({
      experimental__persistedDocuments: {
        cdn: {
          endpoint: 'https://cdn.graphql-hive.com/<target_id>',
          accessToken: '<cdn_access_token>'
        }
      }
    })
    
    // Usage Reporting and Persisted Documents
    useMeshHive({
      token: '<hive_registry_token>',
      experimental__persistedDocuments: {
        cdn: {
          endpoint: 'https://cdn.graphql-hive.com/<target_id>',
          accessToken: '<cdn_access_token>'
        }
      }
    })

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.102.0

0.101.0

Patch Changes

0.100.0

Patch Changes

0.99.7

Patch Changes

  • a1bfc49 Thanks @ardatan! - Removed non-functional `trustProxy` option in the config schema This might cause a non-functional config schemna validation warning This change does not have any impact on the functionality of the Mesh
  • Updated dependencies []:
    • @graphql-mesh/store@0.99.7

0.99.6

Patch Changes

0.99.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.99.5

0.99.4

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.99.4

0.99.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.99.3

0.99.2

Patch Changes

0.99.1

Patch Changes

0.99.0

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.99.0

0.98.10

Patch Changes

  • #7185 0d916a4 Thanks @ardatan! - dependencies updates:

  • #7183 8a04cf7 Thanks @ardatan! - By default, Mesh does not allow extra parameters in the request body other than query, operationName, extensions, and variables, then throws 400 HTTP Error. This change adds a new option called extraParamNames to allow extra parameters in the request body.

    serve:
      extraParamNames:
        - extraParam1
        - extraParam2
    const res = await fetch('/graphql', {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json'
      },
      body: JSON.stringify({
        query: 'query { __typename }',
        extraParam1: 'value1',
        extraParam2: 'value2'
      })
    })
    
    console.assert(res.status === 200)
  • Updated dependencies [0d916a4]:

    • @graphql-mesh/store@0.98.10

0.98.9

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.98.9

0.98.8

Patch Changes

0.98.7

Patch Changes

  • Updated dependencies [19e90eb]:
    • @graphql-mesh/store@0.98.7

0.98.6

Patch Changes

0.98.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.98.5

0.98.4

Patch Changes

  • fb59244 Thanks @ardatan! - Update GraphQL Tools packages

  • Updated dependencies []:

    • @graphql-mesh/store@0.98.4

0.98.3

Patch Changes

  • c47b2aa Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies []:

    • @graphql-mesh/store@0.98.3

0.98.2

Patch Changes

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

  • Updated dependencies [96dd11d]:

    • @graphql-mesh/store@0.98.2

0.98.1

Patch Changes

  • #6903 6044b7f Thanks @ardatan! - Previously GraphQL Yoga also had a health check endpoint in /health path while Mesh’s health check endpoint is /healthcheck. Now they are both aligned. Also now you can customize the health check endpoint within Mesh Configuration using serve.healthCheckEndpoint key. Default value is `/healthcheck.

    serve:
      healthCheckEndpoint: /health

    Action Required: If you are using GraphQL Yoga’s endpoint /health, instead of /healthcheck, you should update your health check endpoint to /health in the configuration like above to keep the behavior.

  • Updated dependencies []:

    • @graphql-mesh/store@0.98.1

0.98.0

Patch Changes

0.97.5

Patch Changes

  • 52f74e7 Thanks @ardatan! - Ability to configure subgraphs

  • Updated dependencies []:

    • @graphql-mesh/store@0.97.5

0.97.4

Patch Changes

  • ff33394 Thanks @ardatan! - Update types in Hive plugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.97.4

0.97.3

Patch Changes

  • 57f4a60 Thanks @ardatan! - Fixes on Prometheus plugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.97.3

0.97.2

Patch Changes

  • 7a712ab Thanks @ardatan! - Track Fusion subgraphs

  • Updated dependencies []:

    • @graphql-mesh/store@0.97.2

0.97.1

Patch Changes

  • #6610 dbaf72c Thanks @ardatan! - New Plugin: Operation Headers

  • Updated dependencies []:

    • @graphql-mesh/store@0.97.1

0.97.0

Minor Changes

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.97.0

0.96.6

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.96.6

0.96.5

Patch Changes

  • #6553 4b3ea1d Thanks @enisdenjo! - Correct additional envelop plugins docs

  • Updated dependencies []:

    • @graphql-mesh/store@0.96.5

0.96.4

Patch Changes

  • #6505 ae7b085 Thanks @EmrysMyrddin! - Allow to configure persisted operations behaviour

  • Updated dependencies []:

    • @graphql-mesh/store@0.96.4

0.96.3

Patch Changes

  • ac26793 Thanks @ardatan! - operationHeaders in Supergraph Handler

  • Updated dependencies []:

    • @graphql-mesh/store@0.96.3

0.96.2

Patch Changes

0.96.1

Patch Changes

  • Updated dependencies [0825974]:
    • @graphql-mesh/store@0.96.1

0.96.0

Minor Changes

  • #6222 5c6a8f784 Thanks @ardatan! - BREAKING: Drop bundles, you can use the SDL output from the artifacts later as a source of the handler

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.96.0

0.95.8

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.95.8

0.95.7

Patch Changes

  • a13969c77 Thanks @ardatan! - Support `deprecated` in OpenAPI and JSON Schemas

  • Updated dependencies []:

    • @graphql-mesh/store@0.95.7

0.95.6

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.95.6

0.95.5

Patch Changes

  • b8f16a42b Thanks @ardatan! - Update types

  • Updated dependencies []:

    • @graphql-mesh/store@0.95.5

0.95.4

Patch Changes

0.95.3

Patch Changes

  • 33ae7a89a Thanks @ardatan! - Cleanup and fix SIGKILL issue

  • Updated dependencies []:

    • @graphql-mesh/store@0.95.3

0.95.2

Patch Changes

  • d8da4b282 Thanks @ardatan! - New autoSelectionSetWithDepth option in the incontext sdk to avoid users to write manual selection sets if return types don’t match
  • Updated dependencies []:
    • @graphql-mesh/store@0.95.2

0.95.1

Patch Changes

  • #5744 7cdc69e04 Thanks @ardatan! - New Supergraph handler

  • Updated dependencies []:

    • @graphql-mesh/store@0.95.1

0.95.0

Minor Changes

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.95.0

0.94.6

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.94.6

0.94.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.94.5

0.94.4

Patch Changes

0.94.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.94.3

0.94.2

Patch Changes

  • #5633 d0d4917f4 Thanks @ardatan! - Request Batching on the gateway

  • Updated dependencies []:

    • @graphql-mesh/store@0.94.2

0.94.1

Patch Changes

  • Updated dependencies [b85a5b1d3]:
    • @graphql-mesh/store@0.94.1

0.94.0

Minor Changes

  • #5342 01fb0cc85 Thanks @cweckesser! - The rename transform uses an ignore list to skip renaming certain types in a schema. It should be possible to manually enable/disable the usage of the exclusion list via configuration.

  • #5449 ef520d91e Thanks @ardatan! - Drop Node 14 support and require Node 16 or higher

Patch Changes

0.93.2

Patch Changes

0.93.1

Patch Changes

1.0.0

Minor Changes

  • #5337 a597261db Thanks @cweckesser! - If a schema defines root types which names are not the standard/expected ones (“Query”, “Mutation” and “Subscription”) when using the encapsulation transform, the encapsulation will not succeed. The proposed solution is to allow parameterizing the root type names, for the cases where they don’t follow the standard/expected ones. The new parameters are optional and have default values (the “standard” values).

Patch Changes

0.91.15

Patch Changes

0.91.14

Patch Changes

0.91.13

Patch Changes

0.91.12

Patch Changes

0.91.11

Patch Changes

0.91.10

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.9.18

0.91.9

Patch Changes

  • #5220 a272fdbca Thanks @ardatan! - Conditional pattern based caching

  • Updated dependencies []:

    • @graphql-mesh/store@0.9.17

0.91.8

Patch Changes

  • Updated dependencies [b86d420d4]:
    • @graphql-mesh/store@0.9.16

0.91.7

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.9.15

0.91.6

Patch Changes

0.91.5

Patch Changes

  • #5153 5c19f8d6f Thanks @ardatan! - Fix createBuiltMeshHTTPHandler’s context generic

  • Updated dependencies []:

    • @graphql-mesh/store@0.9.13

0.91.4

Patch Changes

  • #5145 63ab17f0b Thanks @madorb! - fetchRequestHeaders, fetchResponseHeaders, httpRequestHeaders and httpResponseHeaders

  • Updated dependencies []:

    • @graphql-mesh/store@0.9.12

0.91.3

Patch Changes

0.91.2

Patch Changes

  • 989a47802 Thanks @ardatan! - Options for self hosting

  • Updated dependencies []:

    • @graphql-mesh/store@0.9.10

0.91.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.9.9

0.91.0

Minor Changes

  • 7e8bb87dd Thanks @ardatan! - Allow users to change the version of the federation spec

Patch Changes

0.90.0

Minor Changes

Patch Changes

0.89.5

Patch Changes

0.89.4

Patch Changes

0.89.3

Patch Changes

0.89.2

Patch Changes

0.89.1

Patch Changes

0.89.0

Minor Changes

  • #4767 3edaa00ac Thanks @ardatan! - BREAKING - Neo4J handler’s url changed to endpoint to be consistent with other handlers BREAKING - Neo4J handler’s typeDefs changed to source to be consistent with other handlers BREAKING - OData handler’s url changed to endpoint to be consistent with other handlers BREAKING - OData handler’s metadata changed to source to be consistent with other handlers BREAKING - OpenAPI handler’s baseUrl changed to endpoint to be consistent with other handlers BREAKING - RAML handler’s baseUrl changed to endpoint to be consistent with other handlers BREAKING - RAML handler’s ramlFilePath changed to source to be consistent with other handlers

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.9.1

0.88.0

Minor Changes

Patch Changes

0.87.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.65

0.87.0

Minor Changes

Patch Changes

  • #4854 0d9771428 Thanks @ardatan! - New GraphQL Hive plugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.64

0.86.0

Minor Changes

  • #4789 76deb32d1 Thanks @ardatan! - BREAKING - Local schemas, SDLs and introspections are now provided as source instead of introspection or schema. See the docs for more information.

Patch Changes

0.85.7

Patch Changes

0.85.6

Patch Changes

0.85.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.60

0.85.4

Patch Changes

0.85.3

Patch Changes

0.85.2

Patch Changes

  • 09c286994 Thanks @ardatan! - Fix on handling envelop plugins

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.57

0.85.1

Patch Changes

  • 398af2bf6 Thanks @ardatan! - Fix a bug causing the plugin is registered twice with onPluginInit’s addPlugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.56

0.85.0

Minor Changes

Patch Changes

  • 6fb57d3ba Thanks @ardatan! - Fixes

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.55

0.84.10

Patch Changes

  • #4646 637e9e9d8 Thanks @ardatan! - Fixes for Federation 2 support

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.54

0.84.9

Patch Changes

  • #4638 dd831a7d1 Thanks @ardatan! - Drop Snapshot transform in favor of Snapshot plugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.53

0.84.8

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.52

0.84.7

Patch Changes

0.84.6

Patch Changes

0.84.5

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.49

0.84.4

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.48

0.84.3

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.47

0.84.2

Patch Changes

  • ff251e4c7 Thanks @ardatan! - See the new configuration schema for the new options

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.46

0.84.1

Patch Changes

  • Updated dependencies [b444a9c1c]:
    • @graphql-mesh/store@0.8.45

0.84.0

Minor Changes

Patch Changes

  • #4499 077e65c18 Thanks @ardatan! - New Operation Field Permissions plugin

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.44

0.83.5

Patch Changes

  • Updated dependencies [add1020c9]:
    • @graphql-mesh/store@0.8.43

0.83.4

Patch Changes

0.83.3

Patch Changes

0.83.2

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.40

0.83.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.39

0.83.0

Minor Changes

  • 44b868196 Thanks @ardatan! - Use In Context SDK for wrapping resolvers for better tracing

Patch Changes

  • #4451 a56ebcec5 Thanks @ardatan! - Fix TypeScript typings for additional scalars;

    For example;

    • BigInt should be bigint
    • PositiveInt should be int
    • File should be File
    • NonEmptyString should be string
    • DateTime should be Date
  • 24afabece Thanks @ardatan! - Enable Automatic Type Merging by default

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.38

0.82.3

Patch Changes

0.82.2

Patch Changes

  • #4440 b9bb80094 Thanks @ardatan! - Bump graphql-compose to fix incompatibility issues with non Node.js environments

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.36

0.82.1

Patch Changes

  • #4422 3165827f7 Thanks @ardatan! - 🚀🚀🚀 New StatsD plugin 🚀🚀🚀

    You can learn more about tracing and monitoring in GraphQL with different plugins (StatsD, Prometheus, NewRelic and more) in our documentation. Tracing and Monitoring in GraphQL Mesh

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.35

0.82.0

Minor Changes

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.34

0.81.0

Minor Changes

Patch Changes

0.80.2

Patch Changes

  • #4357 be79b20a5 Thanks @gilgardosh! - ## Breaking changes

    OpenAPI has been completely rewritten based on JSON Schema handler from scratch. It’s now more stable and supports more features. However, it produces different output and takes different configuration options.

    Please check the migration guide to learn how to migrate your existing OpenAPI handler configuration. Migration Guide from 0.31 to 0.32

    This rewrite has been done under @graphql-mesh/new-openapi name so far, and you can check its changelog to see the progress. @graphql-mesh/new-openapi’s CHANGELOG

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.32

0.80.1

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.31

0.80.0

Minor Changes

  • #4327 f882aca38 Thanks @gilgardosh! - ## BREAKING CHANGES
    • Named types are no longer deduplicated automatically, so this might introduce new types on your side. Also the types with unknown content are always reflected as “JSON”/“Any” scalar type
    • noDeduplicate option has been dropped, because it is no longer needed.

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.30

0.79.0

Minor Changes

  • #4235 b162269f7 Thanks @gilgardosh! - - Support “$request.query” and “$request.path” usages in OpenAPI runtime expressions

    • Fix Field not found error when an OpenAPI link refers to an operation which is not Mutation
    • Do not use AJV and check field names in the received object to resolve the type name for a union field
    • Fix queryParams which allows you to pass query parameters for all operations
    • Handle cookie paramters correctly defined in the OpenAPI document by trimming empty values
    • Respect the mime types defined in the OpenAPI document. Now it creates a union for each mime type defined in the document, and resolve it by the mime type.
    • Respect JSON examples given in the OpenAPI document correctly even if they are strings with JSON content.
    • Normalize(lowercase header names) and merge final operation headers correctly from different places operationHeaders from the bundle and configuration plus headers defined for that specific operation.
    • Do not ignore operationHeaders defined in the configuration even if there are some already defined in the bundle

    BREAKING CHANGES:

    • If a JSON Schema type cannot be represented in GraphQL (object without properties etc.), it will no longer use Any type but JSON type instead which is a scalar from graphql-scalars.

    • Due to the improvements in healJSONSchema some of types that are not named in the JSON Schema might be named in a different way. Please make sure the content of the types are correct and report us on GitHub if they are represented incorrectly.

    • UUID format is now represented as UUID scalar type which is a scalar from graphql-scalars.

    • HTTP Errors are now in a more descriptive way. If your consumer respects them strictly, they will probably need to update their implementation.

    {
      "url": "http://www.google.com/api",
      "method": "GET",
    - "status": 401,
    + "statusCode": 401,
    + "statusText": "Unauthorized",
    - "responseJson": {}
    + "responseBody": {}
    }
    • requestSchema and requestSample are no longer used for query parameters in GET operations, but instead we introduced new argTypeMap and queryParamArgMap to define schemas for query parameters.

    For JSON Schema Handler configuration, the following changes are NEEDED;

    - requestSample: { some_flag: true }
    + queryParamArgMap:
    +   some_flag: some_flag
    + argTypeMap:
    +   some_flag:
    +     type: boolean

    or just use the string interpolation;

    path: /mypath?some_flag={args.some_flag}
    • Query parameters no longer uses input, and they become an argument of that operation directly.

    In the generated GraphQL Schema;

    - someOp(input: SomeInput): OpResult
    - input SomeInput {
    -  some_flag: Boolean
    - }
    + someOp(some_flag: Boolean): OpResult
    • argTypeMap no longer takes GraphQL type names but instead it can take JSON Schema pointer or JSON Schema definition itself. New argTypeMap can configure any argument even if it is defined in the headers.
    argTypeMap:
    - some_flag: Boolean
    + some_flag:
    +   type: boolean

Patch Changes

  • Updated dependencies []:
    • @graphql-mesh/store@0.8.29

0.78.8

Patch Changes

0.78.7

Patch Changes

0.78.6

Patch Changes

  • #4216 f95036a33 Thanks @ardatan! - Rewrite JSON Schema visitor and support circular dependencies in a better way

    Now visitJSONSchema takes two different visitor functions instead of enter and leave, previously we used to handle only leave.

    Also generateInterfaceFromSharedFields has been dropped for now because it wasn’t working as expected.

  • Updated dependencies []:

    • @graphql-mesh/store@0.8.26

0.78.5

Patch Changes

0.78.4

Patch Changes

  • @graphql-mesh/store@0.8.24

0.78.3

Patch Changes

  • 738e2f378: Do not visit union elements if links or exposeResponseMetadata is not used during schema generation
    • @graphql-mesh/store@0.8.23

0.78.2

Patch Changes

  • a2ef35c35: ** Use the new @whatwg-node/fetch package instead of cross-undici-fetch**

    cross-undici-fetch has been renamed to @whatwg-node-fetch. Now Mesh uses this new package.

    ** BREAKING: Drop serve.handlers in favor of the new plugin system **

    Now Mesh uses the new plugin system of GraphQL Yoga that uses WHATWG Fetch API instead of Node specific serve.handlers. That means you can use those plugins with any environment even if you are not using Node.js with mesh start.

    Please check our docs to see how you can migrate to the new usage. https://www.graphql-mesh.com/docs/guides/subscriptions-webhooks#handle-webhook-http-requests

    • @graphql-mesh/store@0.8.22

0.78.1

Patch Changes

  • Updated dependencies [2e89d814b]
    • @graphql-mesh/store@0.8.21

0.78.0

Minor Changes

  • bcd9355ee: Breaking change in merger API;

    Before a merger should return a GraphQLSchema, not it needs to return SubschemaConfig from @graphql-tools/delegate package. The idea is to prevent the schema from being wrap to reduce the execution complexity. Now if merger returns an executor, it will be used directly as an executor inside Envelop’s pipeline. Also it can return transforms which will be applied during execution while schema transforms are applied on build time without any modification in the resolvers.

    If there are some root transforms, those are applied together with the source transforms on the execution level in case of a single source.

Patch Changes

  • @graphql-mesh/store@0.8.20

0.77.1

Patch Changes

  • 66f5d0189: New credentials configuration option

    Previously it wasn’t possible to configure credentials of outgoing Request object passed to fetch. And the default behavior was same-origin. Now it is possible to configure it and you can also remove it completely for the environments (e.g. CF Workers) to avoid errors like 'credentials' hasn't been implemented yet etc.

    graphql:
      endpoint: ...
      credentials: disable
    • @graphql-mesh/store@0.8.19

0.77.0

Minor Changes

  • 12e1e5d72: New Cloudflare KV Cache support!

    Now you can basically use Cloudflare Workers’ KV Caching system within Mesh;

    cache:
      cfKv:
        namespace: MESH

    Breaking changes for other cache packages

    Now cache implementations should implement getKeysByPrefix that returns keys starting with the given prefix.

    Response Cache Plugin Improvements

    Response Cache plugin needs some complicated cache storage. So the relational entries related to specific cached responses and entities are now kept as seperate cache entries. Thanks to new getKeysByPrefix, we can now get a response by an entity id for example easier which is more performant.

Patch Changes

  • 12e1e5d72: New Rate Limit plugin
    • @graphql-mesh/store@0.8.18

0.76.0

Minor Changes

  • a0950ac6f: Breaking Change:

    • Now you can set a global customFetch instead of setting customFetch individually for each handler. customFetch configuration field for each handler will no longer work. And also customFetch needs to be the path of the code file that exports the function as default. moduleName#exportName is not supported for now.

    • While programmatically creating the handlers, now you also need fetchFn to be passed to the constructor;

    new GraphQLHandler({
      ...,
      fetchFn: myFetchFn,
    })
    • readFileOrUrl’s second config parameter is now required. Also this second parameter should take an object with cwd, importFn, fetch and logger. You can see the diff of handler’s codes as an example.

Patch Changes

  • @graphql-mesh/store@0.8.17

0.75.0

Minor Changes

  • d4754ad08: Response Cache Plugin

Patch Changes

0.74.2

Patch Changes

  • ed9ba7f48: Small improvements for relaxing event loop
    • @graphql-mesh/store@0.8.15

0.74.1

Patch Changes

  • @graphql-mesh/store@0.8.14

0.74.0

Minor Changes

  • 13b9b30f7: Add interpolation strings to the generated MeshContext type

Patch Changes

  • @graphql-mesh/store@0.8.13

0.73.3

Patch Changes

  • @graphql-mesh/store@0.8.12

0.73.2

Patch Changes

  • @graphql-mesh/store@0.8.11

0.73.1

Patch Changes

  • @graphql-mesh/store@0.8.10

0.73.0

Minor Changes

  • 19a99c055: feat(cli/serve): Now you can configure proxy handling settings

  • 974e703e2: Generate more readable code and cleanup the artifacts

    No more export documentsInSDL, use documents array instead coming from MeshInstance No more export rawConfig but instead rawServeConfig to expose ServeConfig

  • 893d526ab: POC: Mesh Declarative Plugin System

Patch Changes

  • 974e703e2: Cleanup dependencies
  • Updated dependencies [974e703e2]
    • @graphql-mesh/store@0.8.9

0.72.5

Patch Changes

  • @graphql-mesh/store@0.8.8

0.72.4

Patch Changes

  • @graphql-mesh/store@0.8.7

0.72.3

Patch Changes

  • @graphql-mesh/store@0.8.6

0.72.2

Patch Changes

  • Updated dependencies [66b9b3ddc]
    • @graphql-mesh/store@0.8.5

0.72.1

Patch Changes

  • @graphql-mesh/store@0.8.4

0.72.0

Minor Changes

  • fa2542468: Use Localforage by default and drop inmemory-lru

Patch Changes

  • @graphql-mesh/store@0.8.3

0.71.4

Patch Changes

  • @graphql-mesh/store@0.8.2

0.71.3

Patch Changes

  • @graphql-mesh/store@0.8.1

0.71.2

Patch Changes

  • Updated dependencies [8c8b304e5]
    • @graphql-mesh/store@0.8.0

0.71.1

Patch Changes

  • 7856f92d3: Bump all packages
  • Updated dependencies [7856f92d3]
    • @graphql-mesh/store@0.7.8

0.71.0

Minor Changes

  • f963b57ce: Improve Logging Experience
  • 331b62637: feat(json-schema): provide different response schemas for different http status codes

Patch Changes

  • @graphql-mesh/store@0.7.7

0.70.6

Patch Changes

  • @graphql-mesh/store@0.7.6

0.70.5

Patch Changes

  • Updated dependencies [decbe5fbb]
    • @graphql-mesh/store@0.7.5

0.70.4

Patch Changes

  • 35a55e841: Bump GraphQL Tools packages
  • Updated dependencies [35a55e841]
    • @graphql-mesh/store@0.7.4

0.70.3

Patch Changes

  • Updated dependencies [4fa959de3]
    • @graphql-mesh/store@0.7.3

0.70.2

Patch Changes

  • b02f5b008: enhance(cli): leave body parsing to yoga and cache dns with mesh caching
    • @graphql-mesh/store@0.7.2

0.70.1

Patch Changes

  • 2d5c6c72a: add Git repository link in package.json
  • Updated dependencies [2d5c6c72a]
    • @graphql-mesh/store@0.7.1

0.70.0

Minor Changes

  • d567be7b5: feat(json-schema): support bundles from different sources

Patch Changes

  • Updated dependencies [d567be7b5]
    • @graphql-mesh/store@0.7.0

0.69.0

Minor Changes

  • f30dba61e: feat(openapi): add fallbackFormat

Patch Changes

  • @graphql-mesh/store@0.6.2

0.68.3

Patch Changes

  • be61de529: bump dependencies
    • @graphql-mesh/store@0.6.1

0.68.2

Patch Changes

  • b1a6df928: Added @graphql-mesh/transform-hoist-field package
  • Updated dependencies [67fb11706]
    • @graphql-mesh/store@0.6.0

0.68.1

Patch Changes

  • Updated dependencies [b2c537c2a]
    • @graphql-mesh/store@0.5.0

0.68.0

Minor Changes

  • 6c318b91a: New Rate Limit Transform

Patch Changes

  • @graphql-mesh/store@0.4.2

0.67.1

Patch Changes

  • Updated dependencies [4c7b90a87]
    • @graphql-mesh/store@0.4.1

0.67.0

Minor Changes

  • 01bac6bb5: enhance: reduce memory consumption

Patch Changes

  • 01bac6bb5: fix - align graphql-tools versions
  • Updated dependencies [01bac6bb5]
  • Updated dependencies [01bac6bb5]
    • @graphql-mesh/store@0.4.0

0.66.6

Patch Changes

  • @graphql-mesh/store@0.3.29

0.66.5

Patch Changes

  • 2ffb1f287: fix: json schema reference
    • @graphql-mesh/store@0.3.28

0.66.4

Patch Changes

  • 6d2d46480: bump graphql-tools
    • @graphql-mesh/store@0.3.27

0.66.3

Patch Changes

  • Updated dependencies [f11d8b9c8]
    • @graphql-mesh/store@0.3.26

0.66.2

Patch Changes

  • fb876e99c: fix: bump fixed delegate package
    • @graphql-mesh/store@0.3.25

0.66.1

Patch Changes

  • 98ff961ff: enhance: New Transform Prune to prune schema outside of handlers and other transforms
    • @graphql-mesh/store@0.3.24

0.66.0

Minor Changes

  • 6f07de8fe: feat(graphql): custom fetch strategies

Patch Changes

  • 6f07de8fe: fix: do not import process from env
  • b481fbc39: enhance: add tslib to dependencies to reduce bundle size
  • Updated dependencies [b481fbc39]
    • @graphql-mesh/store@0.3.23

0.65.0

Minor Changes

  • 21de17a3d: feat(json-schema): ability to provide additional request body with requestBaseBody in the config

Patch Changes

  • @graphql-mesh/store@0.3.22

0.64.2

Patch Changes

  • 8b8eb5158: feat(naming-convention): add support for fieldArgumentNames
  • 8b8eb5158: feat(transforms): rename support for ObjectFieldArguments
    • @graphql-mesh/store@0.3.21

0.64.1

Patch Changes

  • @graphql-mesh/store@0.3.20

0.64.0

Minor Changes

  • 08b250e04: feat(cli/serve): replace graphql-helix&graphql-upload with graphql-yoga

Patch Changes

  • @graphql-mesh/store@0.3.19

0.63.1

Patch Changes

  • 1815865c3: fix: bump fixed graphql-tools
  • Updated dependencies [1815865c3]
    • @graphql-mesh/store@0.3.18

0.63.0

Minor Changes

  • b6eca9baa: feat(serve): use YogaGraphiQL instead of custom GraphiQL package
  • b6eca9baa: feat(core): Envelop integration

Patch Changes

  • @graphql-mesh/store@0.3.17

0.62.2

Patch Changes

  • 0d43ecf19: fix(runtime): add mock info if not present
    • @graphql-mesh/store@0.3.16

0.62.1

Patch Changes

  • 447bc3697: fix(types): add missing store dependency
    • @graphql-mesh/store@0.3.15

0.62.0

Minor Changes

  • 240ec7b38: feat(openapi): selectQueryOrMutationField flag to choose what field belongs to what root type

0.61.0

Minor Changes

  • 66ca1a366: feat(cli): ability to provide custom codegen config

0.60.0

Minor Changes

  • a79268b3a: feat(raml): ability to select operation type by fieldname

Patch Changes

  • a79268b3a: enhance(types): more strict incontext sdk types

0.59.0

Minor Changes

  • 020431bdc: feat(json-schema/openapi/raml): respect error status codes
  • 020431bdc: feat(redis): fallback to inmemory cache and support env interpolation
  • 020431bdc: feat(cli): built-in typescript support

0.58.0

Minor Changes

  • 6bb4cf673: feat(prefix): allow to prefix only fields

0.57.2

Patch Changes

  • 1ab0aebbc: feat(json-schema): better error handling

0.57.1

Patch Changes

  • d907351c5: new OpenAPI Handler

0.57.0

Minor Changes

  • cfca98d34: feat(utils): drop graphql-subscriptions and use events for PubSub Impl

0.56.0

Minor Changes

  • ec0d1d639: enhance: avoid sync require but collect import sync

0.55.0

Minor Changes

  • 1b332487c: feat(soap): ability to select query or mutation

0.54.1

Patch Changes

  • 761b16ed9: fix(serve): fix critical bug

0.54.0

Minor Changes

  • 09f81dd74: GraphQL v16 compatibility
  • 09f81dd74: GraphQL v16 compability

0.53.0

Minor Changes

  • 6f57be0c1: feat(json-schema): expose GraphQL Tools loader compatible with loadSchema

0.52.0

Minor Changes

  • 811960cdc: feat(runtime): use factory functions for debug messages
  • 6f5ffe766: Add rename functionality to replace-field transform

0.51.0

Minor Changes

  • 256abf5f7: enhance: do not use context of orchestrator but internally

0.50.0

Minor Changes

  • 8c9b709ae: Introduce new replace-field transform

0.49.0

Minor Changes

  • 6ce43ddac: feat(type-merging): additional type merging configuration for edge cases

0.48.0

Minor Changes

  • 67552c8f8: feat(types): update prefix transform

0.47.0

Minor Changes

  • 9eff8a396: enhance(logging): ability to filter debug messages

0.46.0

Minor Changes

  • 4545fe72d: Some improvements on additional resolvers;

    • Now you can point to the nested fields in keyArgs; e.g. keysArg: "where.ids"
    • You don’t need returnType for abstract types anymore, because it’s inferred from the type of targetFieldName.
  • f23820ed0: feat(types): update in-context SDK types

  • 06d688e70: feat(config): new skipSSLValidation configuration field that disabled SSL check on HTTP requests

0.45.2

Patch Changes

  • fc51c574d: Dependency updates

0.45.1

Patch Changes

  • 1c2667489: fix(graphql): Replace old flags with subscriptionsProtocol

0.45.0

Minor Changes

  • 6266d1774: feat(cli): ability to use a custom server handler
  • 2b8dae1cb: feat(cli): generate operations for sdk

Patch Changes

  • 94606e7b9: Enable flags for regular expressions in rename transform

0.44.2

Patch Changes

  • 25d10cc23: fix(types): do not resolve json module

0.44.1

Patch Changes

  • 49c8ceb38: fix(core): bump packages to fix variables issue

0.44.0

Minor Changes

  • 1ee417e3d: feat(mysql): ability to select some specific tables

0.43.0

Minor Changes

  • 885ea439a: New MeshStore approach

Patch Changes

  • d8051f87d: GraphQLHandler endpoint validation

0.42.0

Minor Changes

  • cfb517b3d: feat(types): make baseDir optional

0.41.1

Patch Changes

  • e6acdbd7d: enhance(runtime): do not compose unnecessary resolvers

0.41.0

Minor Changes

  • 214b7a23c: feat(runtime): Type Merging support

0.40.0

Minor Changes

  • 0d2f7bfcd: Added the config option useWebSocketLegacyProtocol for the graphql handler that enables the use of the graphql-ws protocol for subscriptions to the handlers source.

0.39.0

Minor Changes

  • 6c90e0e39: Add wrap mode to resolvers-composition transform (#1928)

0.38.0

Minor Changes

  • 346fe9c61: Performance improvements and OData fixes

0.37.0

Minor Changes

  • 4b57f7496: feat(serve): ability to configure opening browser window feature
  • 4b57f7496: support introspection cache

0.36.1

Patch Changes

  • b77148a04: fix(npm-publish): bump all versions to publish again

0.36.0

Minor Changes

  • 634a8a134: feat(config): introduce introspection cache

Patch Changes

  • 6b8b23a4e: feat(openapi): allow source spec inline injection

0.35.1

Patch Changes

  • 191a663a: fix(types): endpoint doesn’t need to be required

0.35.0

Minor Changes

  • b9ca0c30: Make Transforms and Handlers base-dir aware

0.34.1

Patch Changes

  • 55327fd6: fix(config): support arrays and singular values for additionalTypeDefs

0.34.0

Minor Changes

  • 76051dd7: feat(serve): ability to change GraphQL endpoint path

0.33.0

Minor Changes

  • 646d6bdb: feat(rename-transform): add bare option

0.32.0

Minor Changes

  • 68d6b117: feat(postgraphile): add ability to disable live queries and subscriptions

0.31.1

Patch Changes

  • 212f2d66: fix(postgraphile): caching

0.31.0

Minor Changes

  • 77327988: feat(runtime): Live Queries Support

0.30.1

Patch Changes

  • 48f38a4a: fix(config): allow array of strings in cors configuration

0.30.0

Minor Changes

  • 938cca26: feat(json-schema): allow custom error property with errorMessageField

0.29.4

Patch Changes

  • 8ef29de1: feat(soap): ability to provide custom headers

0.29.3

Patch Changes

  • a02d86c3: feat(serve): add HTTPS support
  • a02d86c3: fix(runtime): patch graphql-compose schemas to support @defer and @stream
  • a02d86c3: feat(serve): ability to change binding hostname

0.29.2

Patch Changes

  • 8e8848e1: feat(serve): ability to change maxRequestBodySize

0.29.1

Patch Changes

  • e8994875: feat(serve): ability to change maxFileSize and maxFiles for graphql-upload

0.29.0

Minor Changes

  • 183cfa96: feat(grpc): add reflection and file descriptor set support

    This change adds two new features to the gRPC handler.

    • Reflection support
    • File descriptor set support

    Both of these features make it easier for graphql-mesh to automatically create a schema for gRPC.

    useReflection: boolean

    This config option enables graphql-mesh to generate a schema by querying the gRPC reflection endpoints. This feature is enabled by the grpc-reflection-js package.

    descriptorSetFilePath: object | string

    This config option enabled graphql-mesh to generate a schema by importing either a binary-encoded file descriptor set file or a JSON file descriptor set file. This config works just like protoFilePath and can be a string or an object containing the file and proto loader options.

    Binary-encoded file descriptor sets can be created by using protoc with the --descriptor_set_out option. Example:

    protoc -I . --descriptor_set_out=./my-descriptor-set.bin ./my-rpc.proto

    JSON file descriptor sets can be created using protobufjs/protobuf.js.

Patch Changes

  • c767df01: fix(fs): fix fs handling issues for non Node environments

0.28.0

Minor Changes

  • a22fc6f3: feat(openapi): customize target root type for an operation and generic payload argument name

0.27.0

Minor Changes

  • c1de3e43: feat(cli): add playground option to serve configuration

0.26.0

Minor Changes

  • 75f6dff9: feat(graphql): ability to disable batch execution
  • c4f207a7: feat(postgraphile): ability to provide custom pgPool instance

0.25.0

Minor Changes

  • 0df817d0: feat(graphql): support exported schemaHeaders

0.24.0

Minor Changes

  • b6262481: feat(snapshot): add respectSelectionSet for advanced snapshot

0.23.3

Patch Changes

  • e5b38574: introduce extend transform

0.23.2

Patch Changes

  • c614e796: fix(types): fix config schema

0.23.1

Patch Changes

  • 59d77fb8: fix(encapsulate): fix transform config

0.23.0

Minor Changes

  • e5cd44f5: feat(rename): support rename transform

0.22.0

Minor Changes

  • 2fd59a83: feat(graphql): add useSSEForSubscription option to use SSE for Subscriptions instead of WebSocket

0.21.1

Patch Changes

  • c064e3a8: Fix minor issues with schema wrapping, updated types

0.21.0

Minor Changes

  • 03f41cd0: feat(graphql): support exported GraphQLSchema from code files

0.20.1

Patch Changes

  • 1e7fd602: feat(graphql): add multipart option to support file uploads

0.20.0

Minor Changes

  • 2d14fcc3: bump graphql-tools to v7

Patch Changes

  • 2d14fcc3: fix(json-schema): make method optional to create nonexecutable schema

0.19.0

Minor Changes

  • c1b073de: feat(runtime): support TypedDocumentNode

0.18.0

Minor Changes

  • 5628fb14: feat(mysql): add an ability to use existing Pool instance

0.17.1

Patch Changes

  • 0560e806: feat(fhir): new FHIR handler

0.17.0

Minor Changes

  • c26c8c56: feat(json-schema): support baseSchema

0.16.1

Patch Changes

  • 3770af72: feat(openapi): addLinitArgument is configurable

    fix(openapi): auto generated limit value is not mandatory

    fix(openapi): generate limit parameter for composed types

0.16.0

Minor Changes

  • 3ee10180: feat(json-schema): add argTypeMap to operation config to provide custom types for args

0.15.0

Minor Changes

  • 0f17c58c: feat(openapi): handle callbacks as subscriptions

0.14.1

Patch Changes

  • 937c87d2: Add ‘useHTTPS’ flag to gRPC config to allow SSL connections without providing a root CA

0.14.0

Minor Changes

  • 1e0445ee: feat(neo4j): add typeDefs option to provide custom schema

0.13.0

Minor Changes

  • b50a68e3: feat(serve): support cookies and static file serving

0.12.0

Minor Changes

  • e2b34219: improve introspection caching
  • 9a7a55c4: feat(openapi): add sourceFormat option to provide schema format explicitly

0.11.3

Patch Changes

  • 2dedda3c: enhance(json-schema): support programmatic json schemas and improve caching
  • a3b42cfd: fix(runtime): handle transforms correctly for single source

0.11.2

Patch Changes

  • 6d624576: fix(types): fix Any scalar type in json schema

0.11.1

Patch Changes

  • 405cec23: enhance(types): improve typings for PubSub

0.11.0

Minor Changes

  • 48d89de2: feat(runtime): replace hooks with pubsub logic

0.10.0

Minor Changes

  • 79adf4b6: feat(config): support functions as config property

0.9.2

Patch Changes

  • 2d5cc25b: chore(types): update config schema

0.9.1

Patch Changes

  • 93ad5255: fix(json-schema): update types

0.9.0

Minor Changes

  • c8d9695e: feat(cli): support —require flag to load dotenv etc

0.8.1

Patch Changes

  • d2e56567: fix(merging): prune schema while merging

0.8.0

Minor Changes

  • a789c312: feat(stitching): use batch execution

0.7.0

Minor Changes

  • 718e7a16: fix(runtime): fix browser support

0.6.0

Minor Changes

  • a76d74bb: feat(config): able to configure serve command in mesh config file

Patch Changes

  • 5067ac73: fix(serve): fix typo

0.5.1

Patch Changes

  • dde7878b: fix(runtime): handle empty arrays

0.5.0

Minor Changes

  • 705c4626: introduce an independent config package

0.4.0

Minor Changes

  • 6f21094b: feat(postgraphile): add more configuration options

Patch Changes

  • 854dc550: fix(localforage-cache): handle ttl better

0.3.1

Patch Changes

  • 3c131332: feat(cache): introduce new caching strategy localforage

0.3.0

Minor Changes

  • ccede377: Introduce includeHttpDetails to include HTTP response details to the result