Bump @graphql-tools/schema from 8.3.3 to 9.0.1

[dependabot]

Bumps @graphql-tools/schema from 8.3.3 to 9.0.1.

Release notes

Sourced from @​graphql-tools/schema's releases.

@​graphql-tools/schema@​8.5.1

Patch Changes

• Updated dependencies [2a3b45e3]
  • @​graphql-tools/utils@​8.9.0
  • @​graphql-tools/merge@​8.3.1

@​graphql-tools/schema@​8.5.0

Minor Changes

• d76a299c: Support TypeScript module resolution.

Patch Changes

• Updated dependencies [a0abbbcd]
• Updated dependencies [d76a299c]
  • @​graphql-tools/utils@​8.8.0
  • @​graphql-tools/merge@​8.3.0

@​graphql-tools/schema@​8.4.0

Minor Changes

• 4914970b: mergeSchemas was skipping defaultFieldResolver and defaultMergedResolver by default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So new includeDefaultMergedResolver flag is introduced in getResolversFromSchema to put default "proxy" resolvers in the extracted resolver map for mergeSchemas.

  This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing defaultMergedResolver in the final merged schema which should come from the wrapped schema.

Patch Changes

• Updated dependencies [4914970b]
  • @​graphql-tools/utils@​8.7.0
  • @​graphql-tools/merge@​8.2.15

Changelog

Sourced from @​graphql-tools/schema's changelog.

9.0.1

Patch Changes

• #4643 2609d71f Thanks @​ardatan! - Revert the breaking change introduced in @graphql-tools/merge

• Updated dependencies [2609d71f]:

  • @​graphql-tools/utils@​8.10.0
  • @​graphql-tools/merge@​8.3.3

9.0.0

Major Changes

• #4463 8cc8721f Thanks @​ardatan! - Thanks @​mattkrick and @​borisno2!

  Breaking changes

  addResolversToSchema;

  If you are using the legacy parameters like below, you should update them to the new usage. Other than that, there is no functional change;

  // From
  addResolversToSchema(schema, resolvers, resolverValidationOptions);
  // To
  addResolversToSchema({
  schema,
  resolvers,
  resolverValidationOptions,
  });

  mergeSchemas;

  The provided resolver overrides the resolvers in the schema with the same name;

  The hello resolver in the schema would be overridden by the hello resolver in the resolvers. Before it was opposite which is not expected.

  const schema = makeExecutableSchema({
    typeDefs: `
      type Query {
        hello: String
      }
    `,
    resolvers: {
      Query: {
        hello: () => 'Hello world!',

... (truncated)

Commits

• d3de883 chore(release): update monorepo packages versions (#4644)
• 2609d71 Revert the breaking change introduces in (#4643)
• 9e80640 chore(release): update monorepo packages versions (#4625)
• 8cc8721 Fix Merge Schemas behavior and remove legacy signature in addResolversToSchem...
• e3167ed fix: typescript commonjs module resolution with node16,nodenext (#4624)
• fbb0709 chore(release): update monorepo packages versions (#4604)
• b9b8dd7 chore(release): update monorepo packages versions (#4542)
• d76a299 feat: support TypeScript esm + esm and cjs import tests on CI (#4539)
• d8558da chore(release): update monorepo packages versions (#4534)
• 4914970 Introduce 'batch' flag, improve loadSchema and merge wrapped schemas properly...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #157.