|
1 | 1 | # graphql-tools
|
2 | 2 |
|
| 3 | +## 9.0.19 |
| 4 | + |
| 5 | +### Patch Changes |
| 6 | + |
| 7 | +- Updated dependencies []: |
| 8 | + - @graphql-tools/schema@10.0.24 |
| 9 | + |
3 | 10 | ## 9.0.18
|
4 | 11 |
|
5 | 12 | ### Patch Changes
|
|
498 | 505 | - a9254491: - Resolver validation options should now be set to `error`, `warn` or `ignore` rather
|
499 | 506 | than `true` or `false`. In previous versions, some of the validators caused errors to be thrown,
|
500 | 507 | while some issued warnings. This changes brings consistency to validator behavior.
|
501 |
| - |
502 | 508 | - The `allowResolversNotInSchema` has been renamed to `requireResolversToMatchSchema`, to
|
503 | 509 | harmonize the naming convention of all the validators. The default setting of
|
504 | 510 | `requireResolversToMatchSchema` is `error`, matching the previous behavior.
|
505 |
| - |
506 | 511 | * The `delegateToSchema` return value has matured and been formalized as an `ExternalObject`, in
|
507 | 512 | which all errors are integrated into the GraphQL response, preserving their initial path. Those
|
508 | 513 | advanced users accessing the result directly will note the change in error handling. This also
|
|
530 | 535 |
|
531 | 536 | * `applySchemaTransforms` parameters have been updated to match and support the `transformSchema`
|
532 | 537 | parameters above.
|
533 |
| - |
534 | 538 | - `wrapSchema` and `generateProxyingResolvers` now only take a single options argument with named
|
535 | 539 | properties of type `SubschemaConfig`. The previously possible shorthand version with first
|
536 | 540 | argument consisting of a `GraphQLSchema` and second argument representing the transforms should
|
|
564 | 568 | parsed SDL rather than strings, to nudge end users to parse these strings at build time (when
|
565 | 569 | possible), rather than at runtime. Parsing of selection set strings can be performed using the
|
566 | 570 | `parseSelectionSet` function from `@graphql-tools/utils`.
|
567 |
| - |
568 | 571 | * `stitchSchemas`'s `mergeTypes` option is now true by default! This causes the `onTypeConflict`
|
569 | 572 | option to be ignored by default. To use `onTypeConflict` to select a specific type instead of
|
570 | 573 | simply merging, simply set `mergeTypes` to false.
|
|
583 | 586 | used. Signatures of the `onTypeConflict`, `fieldConfigMerger`, and `inputFieldConfigMerger` have
|
584 | 587 | been updated to include metadata related to the original and transformed subschemas. Note the
|
585 | 588 | property name change for `onTypeConflict` from `schema` to `subschema`.
|
586 |
| - |
587 | 589 | - Mocks returning objects with fields set as functions are now operating according to upstream
|
588 | 590 | graphql-js convention, i.e. these functions take three arguments, `args`, `context`, and `info`
|
589 | 591 | with `parent` available as `this` rather than as the first argument.
|
590 |
| - |
591 | 592 | * `filterSchema`'s `fieldFilter` will now filter _all_ fields across Object, Interface, and Input
|
592 | 593 | types. For the previous Object-only behavior, switch to the `objectFieldFilter` option.
|
593 | 594 | * Unused `fieldNodes` utility functions have been removed.
|
|
0 commit comments