Mesh
On this page

@graphql-mesh/utils

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

0.107.1

Patch Changes

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

0.107.0

Patch Changes

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

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)

Patch Changes

  • #9606 a7cbeef Thanks @dependabot! - dependencies updates:

  • #9437 e148b13 Thanks @ardatan! - Fix @resolveTo inferring sourceSelectionSet from a result path when the source field is missing from the gateway schema. Encapsulate (and similar transforms) keep the real source field as an @inaccessible copy such as _encapsulated_<name>_<field>, which federation then strips from the supergraph. The client selection set is still wrapped with the result path instead of crashing on sourceField.type.

  • Updated dependencies [07c7b8e]:

    • @graphql-mesh/types@0.106.0

0.105.1

Patch Changes

0.105.0

Patch Changes

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

0.104.38

Patch Changes

0.104.37

Patch Changes

  • #9470 1da4b45 Thanks @dependabot! - dependencies updates:

  • #9490 fa18e2d Thanks @dependabot! - dependencies updates:

  • #9511 7cfc2a0 Thanks @kpiotr! - Fix key-based (batch) additional resolvers delegating with a null key

    A key-based additional resolver (what mesh-compose emits for @resolveTo / BatchResolveTo with keyField + keysArg) resolves a relationship field by looking up the parent’s key field in another subgraph. When the parent’s key field value was null/undefined — a legitimately nullable foreign key — the in-context SDK’s if (key && argsFromKeys) gate treated the nullish key as “no batch” and fell through to the keyless regular delegation path. That emitted an arg-less query to the source subgraph (no keysArg built); if the source field’s argument is optional the subgraph accepted the call and returned its list (often []), which was then projected onto a singular target field, surfacing as Cannot return null for non-nullable field <Type>.<field>..

    batchDelegateToSchema already short-circuits if (key == null) return null;, but the gate diverted nullish keys away before that guard could apply. The in-context SDK now resolves a nullish key (key == null) to null before delegating.

  • Updated dependencies [06c0dee, 1da4b45, fa18e2d]:

    • @graphql-mesh/string-interpolation@0.5.17
    • @graphql-mesh/types@0.104.29

0.104.36

Patch Changes

0.104.35

Patch Changes

0.104.34

Patch Changes

0.104.33

Patch Changes

0.104.32

Patch Changes

  • Updated dependencies [94fbfbd]:
    • @graphql-mesh/string-interpolation@0.5.16

0.104.31

Patch Changes

  • Updated dependencies [339c32c]:
    • @graphql-mesh/string-interpolation@0.5.15

0.104.30

Patch Changes

  • Updated dependencies [3ad6a00]:
    • @graphql-mesh/string-interpolation@0.5.14

0.104.29

Patch Changes

  • Updated dependencies [13af2ff]:
    • @graphql-mesh/string-interpolation@0.5.13

0.104.28

Patch Changes

0.104.27

Patch Changes

0.104.26

Patch Changes

  • Updated dependencies [5d38d11]:
    • @graphql-mesh/string-interpolation@0.5.12

0.104.25

Patch Changes

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

0.104.24

Patch Changes

0.104.23

Patch Changes

0.104.22

Patch Changes

0.104.21

Patch Changes

  • Updated dependencies [0028f3b]:
    • @graphql-mesh/string-interpolation@0.5.11

0.104.20

Patch Changes

0.104.19

Patch Changes

  • Updated dependencies [30e8e32]:
    • @graphql-mesh/string-interpolation@0.5.10

0.104.18

Patch Changes

0.104.17

Patch Changes

0.104.16

Patch Changes

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

0.104.15

Patch Changes

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

0.104.14

Patch Changes

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

0.104.13

Patch Changes

0.104.12

Patch Changes

  • #8747 ffec6e7 Thanks @ardatan! - Export PubSub resolver factory

  • Updated dependencies []:

    • @graphql-mesh/types@0.104.12

0.104.11

Patch Changes

  • #8740 d61faf0 Thanks @enisdenjo! - Resolve fields from other subschemas when merging types from subscriptions in additional type defs

  • Updated dependencies []:

    • @graphql-mesh/types@0.104.11

0.104.10

Patch Changes

  • #8736 7852ccd Thanks @enisdenjo! - Auto merge types from subscriptions in additional type defs

    This means that the sourceName directive does not need to be provided to the @resolveTo directive, instead the resolver will automatically find the subgraph that requires fields available in the subscription event.

    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"
      )
    }
  `
})

  • #8736 7852ccd Thanks @enisdenjo! - The context can be undefined while resolving additional resolvers

  • Updated dependencies []:

    • @graphql-mesh/types@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 [0c18fe1]:

    • @graphql-mesh/types@0.104.9

0.104.8

Patch Changes

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

  • Updated dependencies [fb6e935, fb6e935]:

    • @graphql-mesh/types@0.104.8

0.104.7

Patch Changes

  • c37c23b Thanks @ardatan! - Fix filterBy expression handling

  • Updated dependencies [c37c23b]:

    • @graphql-mesh/types@0.104.7

0.104.6

Patch Changes

  • e2666bc Thanks @ardatan! - Add asyncDispose symbol property as writable while using makeAsyncDisposable

  • Updated dependencies []:

    • @graphql-mesh/types@0.104.6

0.104.5

Patch Changes

  • #8658 9d61d75 Thanks @enisdenjo! - Run onFetchDone hooks even if onFetch has ended early with a response

  • Updated dependencies []:

    • @graphql-mesh/types@0.104.5

0.104.4

Patch Changes

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

0.104.3

Patch Changes

0.104.2

Patch Changes

  • 1b5d072 Thanks @ardatan! - Accept default logger for wrapFetchWithHooks

  • Updated dependencies []:

    • @graphql-mesh/types@0.104.2

0.104.1

Patch Changes

  • #8475 b6c083c Thanks @PlayAnyData! - Added data loader options, allowing to specify batching behaviour in additionalResolvers. Description available here

  • f416982 Thanks @ardatan! - Rename instruments to instrumentation

  • Updated dependencies []:

    • @graphql-mesh/types@0.104.1

0.104.0

Minor Changes

Patch Changes

0.103.21

Patch Changes

0.103.20

Patch Changes

0.103.19

Patch Changes

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

0.103.18

Patch Changes

0.103.17

Patch Changes

  • eee582a Thanks @ardatan! - Add changeset

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.17

0.103.16

Patch Changes

0.103.15

Patch Changes

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

0.103.14

Patch Changes

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

0.103.13

Patch Changes

0.103.12

Patch Changes

0.103.11

Patch Changes

0.103.10

Patch Changes

  • #8176 b750a41 Thanks @iamchanii! - Fix to invoke applySchemaTransforms when creating inContextSDK

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.10

0.103.9

Patch Changes

  • #8150 10ba2c4 Thanks @ardatan! - Fix support for bundling environments like Next.js Regression introduced in #8082
  • Updated dependencies []:
    • @graphql-mesh/types@0.103.9

0.103.8

Patch Changes

  • #8082 93fb364 Thanks @ardatan! - Import enhancements

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.8

0.103.7

Patch Changes

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

0.103.6

Patch Changes

0.103.5

Patch Changes

  • #8007 9f9f6fe Thanks @ardatan! - Always pass a valid info

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.5

0.103.4

Patch Changes

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

0.103.3

Patch Changes

  • 6360755 Thanks @ardatan! - Fix missing import

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.3

0.103.2

Patch Changes

  • bfd8929 Thanks @ardatan! - Move `getInContextSDK` from runtime to utils

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.2

0.103.1

Patch Changes

0.103.0

Minor Changes

Patch Changes

  • #7966 0e49907 Thanks @enisdenjo! - DefaultLogger respects the LogLevel.debug

  • Updated dependencies []:

    • @graphql-mesh/types@0.103.0

0.102.13

Patch Changes

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

0.102.12

Patch Changes

0.102.11

Patch Changes

0.102.10

Patch Changes

0.102.9

Patch Changes

  • #7816 fad4d27 Thanks @ardatan! - Fix subscription fields fed by webhooks and defined in `additionalTypeDefs` with `@resolveTo`

  • Updated dependencies []:

    • @graphql-mesh/types@0.102.9

0.102.8

Patch Changes

0.102.7

Patch Changes

0.102.6

Patch Changes

  • #7719 bf588d3 Thanks @EmrysMyrddin! - Allow for static values in additionalArgs instead of only interpolated strings.

  • Updated dependencies []:

    • @graphql-mesh/types@0.102.6

0.102.5

Patch Changes

0.102.4

Patch Changes

0.102.3

Patch Changes

0.102.2

Patch Changes

0.102.1

Patch Changes

0.102.0

Patch Changes

  • Updated dependencies [13fa835, db41f96]:
    • @graphql-mesh/string-interpolation@0.5.6
    • @graphql-mesh/types@0.102.0

0.101.0

Minor Changes

  • #7497 d784488 Thanks @ardatan! - BREAKING: getDirectiveExtensions is no longer exported, import it from @graphql-tools/utils instead

Patch Changes

0.100.0

Minor Changes

  • #7467 a324c5e Thanks @enisdenjo! - Trimming log messages is an option independant of the DEBUG environment variable.

    Instead of trimming messages at 100 characters by default when the DEBUG environment variable is falsy, have the user configure the trim length that is not set by default.

    import { DefaultLogger } from '@graphql-mesh/utils'

const trimmedLogger = new DefaultLogger('my-logger', undefined, 100 /* trim at 100 characters*/)
;``

Patch Changes

0.99.7

Patch Changes

  • Updated dependencies [a1bfc49]:
    • @graphql-mesh/types@0.99.7

0.99.6

Patch Changes

0.99.5

Patch Changes

0.99.4

Patch Changes

  • #7343 597e790 Thanks @ardatan! - Add timestamp to log messages

    [2021-09-29T14:00:00.000Z] XXXX

  • #7343 597e790 Thanks @ardatan! - Prevent logger to have the same log prefixes

  • Updated dependencies []:

    • @graphql-mesh/types@0.99.4

0.99.3

Patch Changes

0.99.2

Patch Changes

0.99.1

Patch Changes

0.99.0

Minor Changes

Patch Changes

0.98.10

Patch Changes

0.98.9

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 @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 []:

    • @graphql-mesh/types@0.98.9

0.98.8

Patch Changes

0.98.7

Patch Changes

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

0.98.6

Patch Changes

0.98.5

Patch Changes

  • #6936 c4d2249 Thanks @ardatan! - Fallback to node:http when uWebSockets.js is not available

  • Updated dependencies []:

    • @graphql-mesh/types@0.98.5

0.98.4

Patch Changes

  • fb59244 Thanks @ardatan! - Update GraphQL Tools packages

  • Updated dependencies [fb59244]:

    • @graphql-mesh/types@0.98.4

0.98.3

Patch Changes

  • c47b2aa Thanks @ardatan! - Bump GraphQL Tools versions

  • Updated dependencies [c47b2aa]:

    • @graphql-mesh/types@0.98.3

0.98.2

Patch Changes

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

  • Updated dependencies [96dd11d]:

    • @graphql-mesh/cross-helpers@0.4.2
    • @graphql-mesh/types@0.98.2

0.98.1

Patch Changes

  • Updated dependencies [3d88cb8, 6044b7f]:
    • @graphql-mesh/string-interpolation@0.5.4
    • @graphql-mesh/types@0.98.1

0.98.0

Minor Changes

Patch Changes

0.97.5

Patch Changes

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

0.97.4

Patch Changes

0.97.3

Patch Changes

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

0.97.2

Patch Changes

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

0.97.1

Patch Changes

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

0.97.0

Minor Changes

Patch Changes

  • 70b05a2 Thanks @enisdenjo! - Fix message too long notice text

  • Updated dependencies [92dce67]:

    • @graphql-mesh/types@0.97.0

0.96.6

Patch Changes

  • 0f274ef Thanks @ardatan! - Prevent ownKeys trap to return the same keys

  • Updated dependencies []:

    • @graphql-mesh/types@0.96.6

0.96.5

Patch Changes

  • Updated dependencies [4b3ea1d]:
    • @graphql-mesh/types@0.96.5

0.96.4

Patch Changes

  • Updated dependencies [ae7b085]:
    • @graphql-mesh/types@0.96.4

0.96.3

Patch Changes

  • Updated dependencies [ac26793]:
    • @graphql-mesh/types@0.96.3

0.96.2

Patch Changes

0.96.1

Patch Changes

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

0.96.0

Patch Changes

  • Updated dependencies [5c6a8f784]:
    • @graphql-mesh/types@0.96.0

0.95.8

Patch Changes

  • Updated dependencies [b4d38c55d]:
    • @graphql-mesh/string-interpolation@0.5.3
    • @graphql-mesh/types@0.95.8

0.95.7

Patch Changes

  • Updated dependencies [a13969c77]:
    • @graphql-mesh/types@0.95.7

0.95.6

Patch Changes

  • Updated dependencies [8e1056cf9]:
    • @graphql-mesh/string-interpolation@0.5.2
    • @graphql-mesh/types@0.95.6

0.95.5

Patch Changes

  • Updated dependencies [b8f16a42b, b8f16a42b]:
    • @graphql-mesh/cross-helpers@0.4.1
    • @graphql-mesh/types@0.95.5

0.95.4

Patch Changes

  • Updated dependencies [625e5d787]:
    • @graphql-mesh/types@0.95.4

0.95.3

Patch Changes

0.95.2

Patch Changes

  • Updated dependencies [d8da4b282]:
    • @graphql-mesh/types@0.95.2

0.95.1

Patch Changes

  • Updated dependencies [7cdc69e04]:
    • @graphql-mesh/types@0.95.1

0.95.0

Patch Changes

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

0.94.6

Patch Changes

  • #5730 d1310cdff Thanks @EmrysMyrddin! - Allow nested objects as sourceArgs argument of @resolveTo and additionalResolvers

  • Updated dependencies []:

    • @graphql-mesh/types@0.94.6

0.94.5

Patch Changes

  • f11e9b307 Thanks @ardatan! - Avoid extra work for isDebug if DEBUG is not defined

  • Updated dependencies []:

    • @graphql-mesh/types@0.94.5

0.94.4

Patch Changes

  • Updated dependencies [ff1678eea]:
    • @graphql-mesh/types@0.94.4

0.94.3

Patch Changes

  • Updated dependencies [fba66c6fc]:
    • @graphql-mesh/string-interpolation@0.5.1
    • @graphql-mesh/types@0.94.3

0.94.2

Patch Changes

  • Updated dependencies [d0d4917f4]:
    • @graphql-mesh/types@0.94.2

0.94.1

Patch Changes

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

0.94.0

Minor Changes

Patch Changes

0.93.2

Patch Changes

0.93.1

Patch Changes

1.0.0

Patch Changes

0.43.23

Patch Changes

0.43.22

Patch Changes

0.43.21

Patch Changes

0.43.20

Patch Changes

  • #5252 c90eb5ac6 Thanks @ardatan! - Make shared packages peer dependency

  • Updated dependencies [c90eb5ac6]:

    • @graphql-mesh/string-interpolation@0.4.3
    • @graphql-mesh/cross-helpers@0.3.4
    • @graphql-mesh/types@0.91.12

0.43.19

Patch Changes

  • Updated dependencies [7e7096695]:
    • @graphql-mesh/types@0.91.11

0.43.18

Patch Changes

  • #5239 3f658a771 Thanks @ardatan! - Support other Map-like interfaces even if they don’t implement WHATWG Headers fully

  • Updated dependencies []:

    • @graphql-mesh/types@0.91.10

0.43.17

Patch Changes

  • Updated dependencies [a272fdbca]:
    • @graphql-mesh/types@0.91.9

0.43.16

Patch Changes

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

0.43.15

Patch Changes

  • #5200 fa2c010c1 Thanks @jtmthf! - Replace lodsash.set with dset

  • Updated dependencies []:

    • @graphql-mesh/types@0.91.7

0.43.14

Patch Changes

0.43.13

Patch Changes

  • Updated dependencies [5c19f8d6f]:
    • @graphql-mesh/types@0.91.5

0.43.12

Patch Changes

  • Updated dependencies [63ab17f0b]:
    • @graphql-mesh/types@0.91.4

0.43.11

Patch Changes

0.43.10

Patch Changes

  • Updated dependencies [975715275, 989a47802]:
    • @graphql-mesh/cross-helpers@0.3.3
    • @graphql-mesh/types@0.91.2

0.43.9

Patch Changes

  • d694ccc1f Thanks @ardatan! - If the field name is empty, put _ as the name

  • Updated dependencies []:

    • @graphql-mesh/types@0.91.1

0.43.8

Patch Changes

0.43.7

Patch Changes

0.43.6

Patch Changes

0.43.5

Patch Changes

0.43.4

Patch Changes

0.43.3

Patch Changes

  • Updated dependencies [deb9912e0]:
    • @graphql-mesh/string-interpolation@0.4.1
    • @graphql-mesh/types@0.89.2

0.43.2

Patch Changes

0.43.1

Patch Changes

  • Updated dependencies [3edaa00ac]:
    • @graphql-mesh/types@0.89.0

0.43.0

Minor Changes

Patch Changes

0.42.9

Patch Changes

  • eba73c626 Thanks @ardatan! - Better ESM support

  • Updated dependencies []:

    • @graphql-mesh/types@0.87.1

0.42.8

Patch Changes

0.42.7

Patch Changes

0.42.6

Patch Changes

0.42.5

Patch Changes

0.42.4

Patch Changes

  • d5f2d950e Thanks @ardatan! - Fix Windows path issues

  • Updated dependencies []:

    • @graphql-mesh/types@0.85.5

0.42.3

Patch Changes

0.42.2

Patch Changes

0.42.1

Patch Changes

  • Updated dependencies [5c87cfc60, 09c286994]:
    • @graphql-mesh/string-interpolation@0.3.3
    • @graphql-mesh/types@0.85.2

0.42.0

Minor Changes

  • #4708 1d61fbcec Thanks @ardatan! - BREAKING:
    • ”:” character is now sanitized as "" instead of “_COLON”
    • If a path starts with a variable like ”{” in an OAS operation, “by_” prefix is no longer added.

Patch Changes

  • Updated dependencies [398af2bf6]:
    • @graphql-mesh/types@0.85.1

0.41.22

Patch Changes

0.41.21

Patch Changes

  • Updated dependencies [637e9e9d8]:
    • @graphql-mesh/types@0.84.10

0.41.20

Patch Changes

  • Updated dependencies [dd831a7d1]:
    • @graphql-mesh/types@0.84.9

0.41.19

Patch Changes

  • 5b44abcd2 Thanks @ardatan! - Revert tiny-lru to fix browser bundle compatibility

  • Updated dependencies []:

    • @graphql-mesh/types@0.84.8

0.41.18

Patch Changes

0.41.17

Patch Changes

0.41.16

Patch Changes

0.41.15

Patch Changes

0.41.14

Patch Changes

0.41.13

Patch Changes

  • Updated dependencies [ff251e4c7]:
    • @graphql-mesh/types@0.84.2

0.41.12

Patch Changes

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

0.41.11

Patch Changes

0.41.10

Patch Changes

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

0.41.9

Patch Changes

0.41.8

Patch Changes

0.41.7

Patch Changes

0.41.6

Patch Changes

0.41.5

Patch Changes

0.41.4

Patch Changes

0.41.3

Patch Changes

  • Updated dependencies [b9bb80094]:
    • @graphql-mesh/types@0.82.2

0.41.2

Patch Changes

  • Updated dependencies [3165827f7]:
    • @graphql-mesh/types@0.82.1

0.41.1

Patch Changes

0.41.0

Minor Changes

Patch Changes

0.40.0

Minor Changes

  • #4356 b5c59ffce Thanks @ardatan! - ## Improvements on outgoing HTTP calls

    • Now Mesh’s default fetch implementation deduplicates the same GET JSON requests in the same execution context
    • You should pass Accept: application/json to make this work.
    • JSON Schema, new OpenAPI and RAML handlers now take GraphQL context as 3rd parameter. If you use customFetch, you can use that value to access Mesh internals such as the incoming Request object.

    HTTP Details in extensions for tracking HTTP calls

    You can add includeHttpDetailsInExtensions: true to your configuration file to get more information about HTTP calls done by Mesh during the execution in extensions field of the response.

    image

Patch Changes

0.39.0

Minor Changes

  • #4353 f23e14eba Thanks @ardatan! - Now CLI reports critical errors with stack traces even if DEBUG isn’t enabled, and error messages are no longer trimmed.

    Schema couldn't be generated because of the following errors:
- - Foo bar is n...
+ - Foo bar is not valid
+ at /somepath/somejsfile.js:123:2
+ at /someotherpath/someotherjs.file:232:4

Patch Changes

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

0.38.1

Patch Changes

  • Updated dependencies [f882aca38]:
    • @graphql-mesh/types@0.80.0

0.38.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 [b162269f7, 2ad667d96]:
    • @graphql-mesh/types@0.79.0
    • @graphql-mesh/string-interpolation@0.3.2

0.37.9

Patch Changes

0.37.8

Patch Changes

0.37.7

Patch Changes

  • #4237 02c018249 Thanks @ardatan! - - Respect pattern of number types
    • Dereference first-level circular dependencies properly in dereferenceObject
    • Do not make the schema single if there is one allOf or anyOf element but with properties
  • Updated dependencies [f95036a33]:
    • @graphql-mesh/types@0.78.6

0.37.6

Patch Changes

  • Updated dependencies [c88a34d82]
    • @graphql-mesh/types@0.78.5

0.37.5

Patch Changes

  • 30d046724: Fix critical issue when there is a single source with a “bare” transform
    • @graphql-mesh/types@0.78.4

0.37.4

Patch Changes

  • Updated dependencies [738e2f378]
    • @graphql-mesh/types@0.78.3

0.37.3

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

  • Updated dependencies [a2ef35c35]

    • @graphql-mesh/types@0.78.2

0.37.2

Patch Changes

  • @graphql-mesh/types@0.78.1

0.37.1

Patch Changes

  • 6e6fd4ab7: Fix path resolution issue on readFileOrUrl that causes a bug while loading files from the file system for building artifacts
  • Updated dependencies [bcd9355ee]
    • @graphql-mesh/types@0.78.0

0.37.0

Minor Changes

  • 0401c7617: Improvements on string interpolation ({env.sth} or {context.headers.sth}) for different environments

    As we mention in most of our docs, we usually expect a key-value header object in the context. But Fetch-like environments don’t have this kind of object but instead Headers object which is a kind Map. Now Mesh can detect this and automatically convert it to the key-value object especially for Yoga users.

    Also Mesh now handles env in a better way for non-Node environments;

    Consider import.meta.env as env if available, else take globalThis as env.

Patch Changes

  • Updated dependencies [66f5d0189]
  • Updated dependencies [0401c7617]
    • @graphql-mesh/types@0.77.1
    • @graphql-mesh/cross-helpers@0.2.0

0.36.1

Patch Changes

  • Updated dependencies [12e1e5d72]
  • Updated dependencies [12e1e5d72]
  • Updated dependencies [12e1e5d72]
    • @graphql-mesh/cross-helpers@0.1.7
    • @graphql-mesh/types@0.77.0

0.36.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

  • 19d06f6c9: Replace micromatch with minimatch and remove file-path-to-url because both has Node specific dependencies which need polyfills and extra setup for non Node environments
  • 19d06f6c9: Remove chalk dependency
  • Updated dependencies [a0950ac6f]
    • @graphql-mesh/types@0.76.0

0.35.7

Patch Changes

  • Updated dependencies [d4754ad08]
  • Updated dependencies [2df026e90]
    • @graphql-mesh/types@0.75.0

0.35.6

Patch Changes

  • ed9ba7f48: Small improvements for relaxing event loop
  • Updated dependencies [ed9ba7f48]
    • @graphql-mesh/types@0.74.2

0.35.5

Patch Changes

  • 41cfb46b4: Dynamically import additional resolvers instead of static imports
    • @graphql-mesh/types@0.74.1

0.35.4

Patch Changes

  • Updated dependencies [13b9b30f7]
    • @graphql-mesh/string-interpolation@0.3.0
    • @graphql-mesh/types@0.74.0

0.35.3

Patch Changes

  • 9733f490c: Do not strip long messages if DEBUG mode enabled
    • @graphql-mesh/types@0.73.3

0.35.2

Patch Changes

  • 3c0366d2c: - Support import.meta.env instead of process.env for browsers
    • Ponyfill util.inspect only if it is not Node env
  • 3c0366d2c: Sanitize ”.” as ”_” instead of “DOT”
  • Updated dependencies [3c0366d2c]
    • @graphql-mesh/cross-helpers@0.1.6
    • @graphql-mesh/types@0.73.2

0.35.1

Patch Changes

  • abe9fcc41: fix(fileURLtoPath): return empty string if url is not valid
    • @graphql-mesh/types@0.73.1

0.35.0

Minor Changes

  • 974e703e2: No longer import entire lodash library but instead individual smaller packages

Patch Changes

  • 974e703e2: Cleanup dependencies
  • 974e703e2: Use deeper lodash imports to have better treeshaking and avoid using eval
  • Updated dependencies [974e703e2]
  • Updated dependencies [19a99c055]
  • Updated dependencies [974e703e2]
  • Updated dependencies [974e703e2]
  • Updated dependencies [893d526ab]
  • Updated dependencies [974e703e2]
    • @graphql-mesh/string-interpolation@0.2.0
    • @graphql-mesh/types@0.73.0
    • @graphql-mesh/cross-helpers@0.1.5

0.34.10

Patch Changes

  • 43eb3d2c2: fix(additionalResolvers): check if result type matches the abstract source type by respecting interface inheritance
    • @graphql-mesh/types@0.72.5

0.34.9

Patch Changes

  • 55ad5ea44: Fix browser support
  • Updated dependencies [55ad5ea44]
    • @graphql-mesh/cross-helpers@0.1.4
    • @graphql-mesh/types@0.72.4

0.34.8

Patch Changes

  • 31efa964e: Fix ESM support
    • @graphql-mesh/types@0.72.3

0.34.7

Patch Changes

  • Updated dependencies [66b9b3ddc]
    • @graphql-mesh/cross-helpers@0.1.3
    • @graphql-mesh/types@0.72.2

0.34.6

Patch Changes

  • b9beacca2: Bump cross-undici-fetch for Node 14 compatibility and performance improvements
    • @graphql-mesh/types@0.72.1

0.34.5

Patch Changes

  • Updated dependencies [fa2542468]
    • @graphql-mesh/types@0.72.0

0.34.4

Patch Changes

  • ddbbec8a8: Supress dynamic import warnings in Vite
    • @graphql-mesh/types@0.71.4

0.34.3

Patch Changes

  • 2e9addd80: Bump cross-undici-fetch for Node 18 compat
  • Updated dependencies [2e9addd80]
  • Updated dependencies [2e9addd80]
    • @graphql-mesh/string-interpolation@0.1.0
    • @graphql-mesh/types@0.71.3

0.34.2

Patch Changes

  • @graphql-mesh/types@0.71.2

0.34.1

Patch Changes

  • 7856f92d3: Bump all packages
  • Updated dependencies [7856f92d3]
    • @graphql-mesh/cross-helpers@0.1.2
    • @graphql-mesh/string-interpolation@0.0.1
    • @graphql-mesh/types@0.71.1

0.34.0

Minor Changes

  • f963b57ce: Improve Logging Experience
  • 0644f31f2: Use dayjs instead of date-fns for smaller bundle size
  • 331b62637: feat(utils): add base64 modifier to string interpolator
  • 331b62637: feat(json-schema/openapi): support OpenAPI links and json pointer syntax in string interpolation
  • 331b62637: feat: support JSON string as an input for string file pointers

Patch Changes

  • Updated dependencies [f963b57ce]
  • Updated dependencies [331b62637]
    • @graphql-mesh/types@0.71.0

0.33.6

Patch Changes

  • Updated dependencies [cf0836a64]
    • @graphql-mesh/cross-helpers@0.1.1
    • @graphql-mesh/types@0.70.6

0.33.5

Patch Changes

  • @graphql-mesh/types@0.70.5

0.33.4

Patch Changes

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

0.33.3

Patch Changes

  • @graphql-mesh/types@0.70.3

0.33.2

Patch Changes

  • Updated dependencies [b02f5b008]
    • @graphql-mesh/types@0.70.2

0.33.1

Patch Changes

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

0.33.0

Minor Changes

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

Patch Changes

  • Updated dependencies [d567be7b5]
    • @graphql-mesh/types@0.70.0

0.32.2

Patch Changes

  • Updated dependencies [f30dba61e]
    • @graphql-mesh/types@0.69.0

0.32.1

Patch Changes

  • Updated dependencies [be61de529]
    • @graphql-mesh/types@0.68.3

0.32.0

Minor Changes

  • 67fb11706: enhance: improve cross-platform support

Patch Changes

  • Updated dependencies [b1a6df928]
    • @graphql-mesh/types@0.68.2

0.31.0

Minor Changes

  • b2c537c2a: feat - cross-platform support

Patch Changes

  • Updated dependencies [b2c537c2a]
    • @graphql-mesh/cross-helpers@0.1.0
    • @graphql-mesh/types@0.68.1

0.30.2

Patch Changes

  • Updated dependencies [6c318b91a]
    • @graphql-mesh/types@0.68.0

0.30.1

Patch Changes

  • @graphql-mesh/types@0.67.1

0.30.0

Minor Changes

  • 01bac6bb5: enhance: reduce memory consumption

Patch Changes

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

0.29.0

Minor Changes

  • 268db0462: feat: persisted queries

Patch Changes

  • @graphql-mesh/types@0.66.6

0.28.5

Patch Changes

  • Updated dependencies [2ffb1f287]
    • @graphql-mesh/types@0.66.5

0.28.4

Patch Changes

  • Updated dependencies [6d2d46480]
    • @graphql-mesh/types@0.66.4

0.28.3

Patch Changes

  • @graphql-mesh/types@0.66.3

0.28.2

Patch Changes

  • fb876e99c: fix: bump fixed delegate package
  • Updated dependencies [fb876e99c]
    • @graphql-mesh/types@0.66.2

0.28.1

Patch Changes

  • Updated dependencies [98ff961ff]
    • @graphql-mesh/types@0.66.1

0.28.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 [6f07de8fe]
  • Updated dependencies [6f07de8fe]
  • Updated dependencies [b481fbc39]
    • @graphql-mesh/types@0.66.0

0.27.9

Patch Changes

  • 3f4bb09a9: fix(applyResultTransforms): apply transformers for result in correct order
  • Updated dependencies [21de17a3d]
    • @graphql-mesh/types@0.65.0

0.27.8

Patch Changes

  • Updated dependencies [8b8eb5158]
  • Updated dependencies [8b8eb5158]
    • @graphql-mesh/types@0.64.2

0.27.7

Patch Changes

  • ca6bb5ff3: fix(utils): convert minus character to underscore if in the middle
    • @graphql-mesh/types@0.64.1

0.27.6

Patch Changes

  • Updated dependencies [08b250e04]
    • @graphql-mesh/types@0.64.0

0.27.5

Patch Changes

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

0.27.4

Patch Changes

  • Updated dependencies [b6eca9baa]
  • Updated dependencies [b6eca9baa]
    • @graphql-mesh/types@0.63.0

0.27.3

Patch Changes

  • Updated dependencies [0d43ecf19]
    • @graphql-mesh/types@0.62.2

0.27.2

Patch Changes

  • c71b29004: fix(utils): revert unnecessary change
  • Updated dependencies [447bc3697]
    • @graphql-mesh/types@0.62.1

0.27.1

Patch Changes

  • fcbd12a35: fix(utils): normalize module objects with Object.defineProperty not with regular assignment
  • Updated dependencies [240ec7b38]
    • @graphql-mesh/types@0.62.0

0.27.0

Minor Changes

  • 900a01355: Support YAML include

0.26.4

Patch Changes

  • Updated dependencies [66ca1a366]
    • @graphql-mesh/types@0.61.0

0.26.3

Patch Changes

  • Updated dependencies [a79268b3a]
  • Updated dependencies [a79268b3a]
    • @graphql-mesh/types@0.60.0

0.26.2

Patch Changes

  • Updated dependencies [020431bdc]
  • Updated dependencies [020431bdc]
  • Updated dependencies [020431bdc]
    • @graphql-mesh/types@0.59.0

0.26.1

Patch Changes

  • 113091148: fix(utils): better error for missing types in incontext sdk
  • Updated dependencies [6bb4cf673]
    • @graphql-mesh/types@0.58.0

0.26.0

Minor Changes

  • 56e2257fa: feat: use JIT in all execution phases

Patch Changes

  • 56e2257fa: fix(merger-bare): handle single source transforms correctly
  • Updated dependencies [1ab0aebbc]
    • @graphql-mesh/types@0.57.2

0.25.0

Minor Changes

  • 2b876f2b8: feat(core): re-enable leaf serialization and custom JSON serializer during execution

0.24.2

Patch Changes

  • d907351c5: new OpenAPI Handler
  • Updated dependencies [d907351c5]
    • @graphql-mesh/types@0.57.1

0.24.1

Patch Changes

  • 26d685f2a: fix(pubsub): get correct value from event

0.24.0

Minor Changes

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

Patch Changes

  • Updated dependencies [cfca98d34]
    • @graphql-mesh/types@0.57.0

0.23.0

Minor Changes

  • 5666484d6: update cross-undici-fetch

0.22.2

Patch Changes

  • 6c216c309: fix(readFileOrUrl): read JSON from FS not CJS

0.22.1

Patch Changes

  • c22eb1b5e: feat(playground): embed GraphQL Mesh logo in GraphiQL

0.22.0

Minor Changes

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

Patch Changes

  • 1cc0acb9a: fix: normalize imported modules
  • Updated dependencies [ec0d1d639]
    • @graphql-mesh/types@0.56.0

0.21.1

Patch Changes

  • Updated dependencies [1b332487c]
    • @graphql-mesh/types@0.55.0

0.21.0

Minor Changes

  • 875d0e48d: enhance: small improvements

0.20.1

Patch Changes

  • Updated dependencies [761b16ed9]
    • @graphql-mesh/types@0.54.1

0.20.0

Minor Changes

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

Patch Changes

  • Updated dependencies [09f81dd74]
  • Updated dependencies [09f81dd74]
    • @graphql-mesh/types@0.54.0

0.19.0

Minor Changes

  • 0dc08e5cc: enhance: improve jitExecutorFactory

0.18.1

Patch Changes

  • Updated dependencies [6f57be0c1]
    • @graphql-mesh/types@0.53.0

0.18.0

Minor Changes

  • 4ec7a14ba: enhance: memoize parse/print document node
  • 811960cdc: feat(runtime): use factory functions for debug messages

Patch Changes

  • Updated dependencies [811960cdc]
  • Updated dependencies [6f5ffe766]
    • @graphql-mesh/types@0.52.0

0.17.2

Patch Changes

  • Updated dependencies [256abf5f7]
    • @graphql-mesh/types@0.51.0

0.17.1

Patch Changes

  • Updated dependencies [8c9b709ae]
    • @graphql-mesh/types@0.50.0

0.17.0

Minor Changes

  • 7bd145769: feat(utils): use JIT for subscriptions as well

0.16.3

Patch Changes

  • 472c5887b: enhance(readFileOrUrl): remove unnecessary caching

0.16.2

Patch Changes

  • Updated dependencies [6ce43ddac]
    • @graphql-mesh/types@0.49.0

0.16.1

Patch Changes

  • 46a4f7b73: fix(utils): hashObject should always return a string
  • aa804d043: enhance(utils): improve rmdirs
  • Updated dependencies [67552c8f8]
    • @graphql-mesh/types@0.48.0

0.16.0

Minor Changes

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

Patch Changes

  • Updated dependencies [9eff8a396]
    • @graphql-mesh/types@0.47.0

0.15.0

Minor Changes

  • f4f30741d: enhance(artifacts): no more execute additional resolvers during build

0.14.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.

  • d189b4034: feat(json-schema): handle non-latin or non-string values correctly

Patch Changes

  • Updated dependencies [4545fe72d]
  • Updated dependencies [f23820ed0]
  • Updated dependencies [06d688e70]
    • @graphql-mesh/types@0.46.0

0.13.7

Patch Changes

  • fc51c574d: Dependency updates
  • Updated dependencies [fc51c574d]
    • @graphql-mesh/types@0.45.2

0.13.6

Patch Changes

  • Updated dependencies [1c2667489]
    • @graphql-mesh/types@0.45.1

0.13.5

Patch Changes

  • 7080a2f1d: Fix baseDir imports for cli generated artifacts

0.13.4

Patch Changes

  • 0c97b4b75: fix(config): Yarn PnP Support
  • Updated dependencies [6266d1774]
  • Updated dependencies [94606e7b9]
  • Updated dependencies [2b8dae1cb]
    • @graphql-mesh/types@0.45.0

0.13.3

Patch Changes

  • Updated dependencies [25d10cc23]
    • @graphql-mesh/types@0.44.2

0.13.2

Patch Changes

  • 49c8ceb38: fix(core): bump packages to fix variables issue
  • Updated dependencies [49c8ceb38]
    • @graphql-mesh/types@0.44.1

0.13.1

Patch Changes

  • Updated dependencies [1ee417e3d]
    • @graphql-mesh/types@0.44.0

0.13.0

Minor Changes

  • 885ea439a: New MeshStore approach

Patch Changes

  • d8051f87d: use fallbackFormat in readUrlWithCache
  • Updated dependencies [885ea439a]
  • Updated dependencies [d8051f87d]
    • @graphql-mesh/types@0.43.0

0.12.0

Minor Changes

  • bdb58dfec: chore(deps): bump object-hash

0.11.4

Patch Changes

  • 7d0e33660: fix(utils): support annotations in argTypeMap

0.11.3

Patch Changes

  • 3c4c51100: enhance(runtime): skip validation on schema delegation

0.11.2

Patch Changes

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

0.11.1

Patch Changes

  • 69c89666d: chore(utils): bump string interpolator version

0.11.0

Minor Changes

  • 1caa8ffd3: enhance(runtime): use graphql-jit to improve the performance

0.10.0

Minor Changes

  • 346fe9c61: Performance improvements and OData fixes

0.9.2

Patch Changes

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

0.9.1

Patch Changes

  • 2c3312f1a: use fallbackFormat in readUrlWithCache
  • d12c7d978: fix(utils): use mkdir before emit output

0.9.0

Minor Changes

  • b9ca0c30: Make Transforms and Handlers base-dir aware

0.8.8

Patch Changes

  • ec89a923: fix(utils): ensure directory exists in writeJSON

0.8.7

Patch Changes

0.8.6

Patch Changes

  • 7e970f09: fix(utils): handle more complex interpolation strings

0.8.5

Patch Changes

  • 8d345721: fix(utils): fix pathExists issue

0.8.4

Patch Changes

  • c767df01: fix(fs): fix fs handling issues for non Node environments
  • b3d7ecbf: chore(deps): replace fs-extra with native fs

0.8.3

Patch Changes

  • 08c2966e: chore(config): update js-yaml

0.8.2

Patch Changes

  • c85a54eb: fix(utils): handle multiple transforms properly

0.8.1

Patch Changes

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

0.8.0

Minor Changes

  • 2d14fcc3: bump graphql-tools to v7

0.7.0

Minor Changes

  • c1b073de: feat(runtime): support TypedDocumentNode

0.6.0

Minor Changes

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

0.5.4

Patch Changes

  • a3b42cfd: fix(runtime): handle transforms correctly for single source

0.5.3

Patch Changes

  • 79adf4b6: fix(utils): loadModuleExpression keep value if not string

0.5.2

Patch Changes

  • 9900d2fa: fix(runtime): handle noWrap transforms correctly
  • 9900d2fa: chore(utils): move groupTransforms under utils

0.5.1

Patch Changes

  • 8f53be10: fix(utils): do not try to parse empty strings

0.5.0

Minor Changes

  • a789c312: feat(stitching): use batch execution

0.4.0

Minor Changes

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

0.3.0

Minor Changes

  • 705c4626: introduce an independent config package