github ardatan/graphql-tools release-1660066351390
Release 9e80640a (from master)
on GitHub

latest releases: release-1732735109178, @graphql-tools/utils@10.6.1, @graphql-tools/url-loader@8.0.17...
2 years ago

@graphql-tools/batch-delegate@8.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc, d8dc67aa]:

    • @graphql-tools/delegate@9.0.0
    • @graphql-tools/utils@8.9.1

@graphql-tools/batch-execute@8.5.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/delegate@9.0.0

Major Changes

  • #4566 d8dc67aa Thanks @ardatan! - ## Breaking changes

    Schema generation optimization by removing transfomedSchema parameter

    Previously we were applying the transforms multiple times. We needed to introduced some breaking changes to improve the initial wrapped/stitched schema generation performance;

    • Transform.transformSchema no longer accepts transformedSchema which can easily be created with applySchemaTransforms(schema, subschemaConfig) instead.
    • Proxying resolver factory function that is passed as createProxyingResolver to SubschemaConfig no longer takes transformedSchema which can easily be created with applySchemaTransforms(schema, subschemaConfig) instead.

    stitchSchemas doesn't take nested arrays of subschemas

    stitchSchemas no longer accepts an array of arrays of subschema configuration objects. Instead, it accepts an array of subschema configuration objects or schema objects directly.

    stitchSchemas no longer prunes the schema with pruningOptions

    You can use pruneSchema from @graphql-tools/utils to prune the schema instead.

    stitchSchemas no longer respect "@computed" directive if stitchingDirectivesTransformer isn't applied

    Also @graphql-tools/stitch no longer exports computedDirectiveTransformer and defaultSubschemaConfigTransforms.
    Instead, use @graphql-tools/stitching-directives package for @computed directive.
    Learn more about setting it up

    computedFields has been removed from the merged type configuration

    MergeTypeConfig.computedFields setting has been removed in favor of new computed field configuration written as: 

    merge: {
  MyType: {
    fields: {
      myComputedField: {
        selectionSet: '{ weight }',
        computed: true,
      }
    }
  }
}

    A field-level selectionSet specifies field dependencies while the computed setting structures the field in a way that assures it is always selected with this data provided. The selectionSet is intentionally generic to support possible future uses. This new pattern organizes all field-level configuration (including canonical) into a single structure.

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [8cc8721f, e3167edc]:

    • @graphql-tools/schema@9.0.0
    • @graphql-tools/batch-execute@8.5.2
    • @graphql-tools/utils@8.9.1

@graphql-tools/graphql-tag-pluck@7.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

graphql-tools@8.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [8cc8721f, e3167edc]:

    • @graphql-tools/schema@9.0.0

@graphql-tools/import@6.7.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/jest-transform@1.2.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/webpack-loader@6.7.1

@graphql-tools/links@8.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc, d8dc67aa]:

    • @graphql-tools/delegate@9.0.0
    • @graphql-tools/utils@8.9.1

@graphql-tools/load@7.7.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [8cc8721f, e3167edc]:

    • @graphql-tools/schema@9.0.0
    • @graphql-tools/utils@8.9.1

@graphql-tools/load-files@6.6.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

@graphql-tools/apollo-engine-loader@7.3.7

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/code-file-loader@7.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/graphql-tag-pluck@7.3.2
    • @graphql-tools/utils@8.9.1

@graphql-tools/git-loader@7.2.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/graphql-tag-pluck@7.3.2
    • @graphql-tools/utils@8.9.1

@graphql-tools/github-loader@7.3.7

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/graphql-tag-pluck@7.3.2
    • @graphql-tools/utils@8.9.1

@graphql-tools/graphql-file-loader@7.5.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/import@6.7.2
    • @graphql-tools/utils@8.9.1

@graphql-tools/json-file-loader@7.4.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/module-loader@7.2.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/prisma-loader@7.2.9

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/url-loader@7.13.4
    • @graphql-tools/utils@8.9.1

@graphql-tools/url-loader@7.13.4

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc, d8dc67aa]:

    • @graphql-tools/delegate@9.0.0
    • @graphql-tools/utils@8.9.1
    • @graphql-tools/wrap@9.0.0

@graphql-tools/merge@8.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/mock@8.7.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [8cc8721f, e3167edc]:

    • @graphql-tools/schema@9.0.0
    • @graphql-tools/utils@8.9.1

@graphql-tools/node-require@6.4.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/load@7.7.2
    • @graphql-tools/graphql-file-loader@7.5.1
    • @graphql-tools/utils@8.9.1

@graphql-tools/optimize@1.3.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

@graphql-tools/relay-operation-optimizer@6.5.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/resolvers-composition@6.5.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/utils@8.9.1

@graphql-tools/schema@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!',
    },
  },
});

mergeSchemas({
  schemas: [schema],
  resolvers: {
    Query: {
      hello: () => 'New hello world',
    },
  },
});

    makeExecutableSchema no longer takes parseOptions and you can pass those options directly; 

    makeExecutableSchema({
  typeDefs: ``,
  parseOptions: {
    assumeValid: true,
  },
});

// After
makeExecutableSchema({
  typeDefs: ``,
  assumeValid: true,
});

    makeExecutableSchema no longer does pruning and it doesn't take pruningOptions anymore.
    You can use pruneSchema from @graphql-tools/utils if you need.

    extractExtensionsFromSchema moved from @graphql-tools/merge to @graphql-tools/schema.
    And travelSchemaPossibleExtensions has been dropped in favor of mapSchema.

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/merge@8.3.2
    • @graphql-tools/utils@8.9.1

@graphql-tools/stitch@8.7.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [8cc8721f, e3167edc, d8dc67aa]:

    • @graphql-tools/schema@9.0.0
    • @graphql-tools/batch-delegate@8.3.2
    • @graphql-tools/delegate@9.0.0
    • @graphql-tools/merge@8.3.2
    • @graphql-tools/utils@8.9.1
    • @graphql-tools/wrap@9.0.0

@graphql-tools/stitching-directives@2.3.2

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc, d8dc67aa]:

    • @graphql-tools/delegate@9.0.0
    • @graphql-tools/utils@8.9.1

@graphql-tools/utils@8.9.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

@graphql-tools/webpack-loader@6.7.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [e3167edc]:

    • @graphql-tools/optimize@1.3.1
    • @graphql-tools/webpack-loader-runtime@6.4.1

@graphql-tools/webpack-loader-runtime@6.4.1

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

@graphql-tools/wrap@9.0.0

Major Changes

  • #4566 d8dc67aa Thanks @ardatan! - ## Breaking changes

    Schema generation optimization by removing transfomedSchema parameter

    Previously we were applying the transforms multiple times. We needed to introduced some breaking changes to improve the initial wrapped/stitched schema generation performance;

    • Transform.transformSchema no longer accepts transformedSchema which can easily be created with applySchemaTransforms(schema, subschemaConfig) instead.
    • Proxying resolver factory function that is passed as createProxyingResolver to SubschemaConfig no longer takes transformedSchema which can easily be created with applySchemaTransforms(schema, subschemaConfig) instead.

    stitchSchemas doesn't take nested arrays of subschemas

    stitchSchemas no longer accepts an array of arrays of subschema configuration objects. Instead, it accepts an array of subschema configuration objects or schema objects directly.

    stitchSchemas no longer prunes the schema with pruningOptions

    You can use pruneSchema from @graphql-tools/utils to prune the schema instead.

    stitchSchemas no longer respect "@computed" directive if stitchingDirectivesTransformer isn't applied

    Also @graphql-tools/stitch no longer exports computedDirectiveTransformer and defaultSubschemaConfigTransforms.
    Instead, use @graphql-tools/stitching-directives package for @computed directive.
    Learn more about setting it up

    computedFields has been removed from the merged type configuration

    MergeTypeConfig.computedFields setting has been removed in favor of new computed field configuration written as: 

    merge: {
  MyType: {
    fields: {
      myComputedField: {
        selectionSet: '{ weight }',
        computed: true,
      }
    }
  }
}

    A field-level selectionSet specifies field dependencies while the computed setting structures the field in a way that assures it is always selected with this data provided. The selectionSet is intentionally generic to support possible future uses. This new pattern organizes all field-level configuration (including canonical) into a single structure.

Patch Changes

  • #4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

  • Updated dependencies [8cc8721f, e3167edc, d8dc67aa]:

    • @graphql-tools/schema@9.0.0
    • @graphql-tools/delegate@9.0.0
    • @graphql-tools/utils@8.9.1
Check out latest releases or
releases around ardatan/graphql-tools release-1660066351390

Don't miss a new graphql-tools release

NewReleases is sending notifications on new releases.

Get notifications