graphql-mesh

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Minor Changes

• b69746d2c: feat(json-schema): new exposeResponseMetadata flag to expose the details of the HTTP responses received from the upstream

  responseSchema: ...
  exposeResponseMetadata: true
  

  Now you will have another field called $response in the response type;

  type MyResponseType {
    myFooField: String
    _response: ResponseMetadata
  }
  
  type ResponseMetadata {
    url: URL
    status: Int
    method: String
    headers: JSON
    body: String
  }
  

Patch Changes

• 12e1e5d72: Do not compile JSON Schemas with ajv if function constructors are not supported. This fixes an issue with Mesh and CF Workers. Previously it throws an error because of "new Function" usage
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • [email protected]
  • @graphql-mesh/[email protected]

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

• Updated dependencies [12e1e5d72]

• Updated dependencies [12e1e5d72]

• Updated dependencies [12e1e5d72]

  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [b69746d2c]
• Updated dependencies [12e1e5d72]
• Updated dependencies [12e1e5d72]
  • @omnigraph/[email protected]
  • @graphql-mesh/[email protected]
  • [email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

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

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]

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/[email protected]

Patch Changes

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

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/[email protected]

Patch Changes

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

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

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • [email protected]
  • @omnigraph/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

Patch Changes

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]

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

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]