graphql-mesh

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]
  • @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]
  • @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]
  • @omnigraph/[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]

Patch Changes

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @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]

Patch Changes

• 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]
  • @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]
  • @graphql-mesh/[email protected]

Patch Changes

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

Minor Changes

• ee592adbf: Directives Approach for Additional Type Definitions and Resolvers;

  Before we use declarative approach for additionalResolvers that is added besides additionalTypeDefs which might be confusing once the project grows.
  And now we introduce new @resolveTo directive which has the same declarative syntax inside the SDL instead of the configuration file.

  Before;

  additionalTypeDefs: |
    extend type Book {
      author: Author
    }
  
  additionalResolvers:
    - targetTypeName: Book
      targetFieldName: author
      sourceName: Author
      sourceTypeName: Query
      sourceFieldName: authorById
      requiredSelectionSet: '{ id }'
      sourceArgs:
        id: '{root.id}'
  

  After:

  extend type Book {
    author: Author @resolveTo(
      sourceName: "Author",
      sourceTypeName: "Query",
      sourceFieldName: "author",
      requiredSelectionSet: "{ id }",
      sourceArgs:
        id: "{root.id}"
    )
  }
  

• 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]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[email protected]
  • @graphql-mesh/[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]
  • [email protected]
  • @omnigraph/[email protected]

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]
  • @graphql-mesh/[email protected]

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
• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @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]

Patch Changes

• Updated dependencies [19d06f6c9]
• Updated dependencies [19d06f6c9]
• Updated dependencies [a0950ac6f]
  • @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]