chore(deps): update graphql-tools #1750
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.0.22->8.1.88.0.20->8.0.258.1.2->8.1.79.1.1->9.1.610.9.1->10.11.0Release Notes
ardatan/graphql-tools (@graphql-tools/graphql-file-loader)
v8.1.8Compare Source
Patch Changes
2118a80Thanks @EmrysMyrddin! - dependencies updates:
@graphql-tools/import@7.1.7↗︎(from
7.1.6, independencies)[
2118a80,92f1622,2118a80]:v8.1.7Compare Source
Patch Changes
[
8a2a507]:v8.1.6Compare Source
Patch Changes
[
2fe123a]:v8.1.5Compare Source
Patch Changes
[
dddc5f6]:v8.1.4Compare Source
Patch Changes
[
fbb58b5]:v8.1.3Compare Source
Patch Changes
[
fd105f4,fded91e,3b99a9b,5265f8e]:v8.1.2Compare Source
Patch Changes
[
41cc67a]:v8.1.1Compare Source
Patch Changes
[
07124d5,211ef44]:v8.1.0Compare Source
Minor Changes
#7310
692cfebThanks @HunterLarco! - GraphQL schemas in large projects,
especially monorepos, suffer from fragile and verbose relative import paths that become difficult
to maintain as projects grow. This change brings TypeScript's popular
tsconfig.json#pathsaliasing syntax to GraphQLimports, enabling clean, maintainable import statements across your GraphQL schema files.
Before - Brittle relative imports:
After - Clean, semantic aliases:
Configuration Example
This change is introduced in a backwards compatible way to ensure no existing use cases are broken
while using familiar patterns to typescript developers for structuring import aliases.
Patch Changes
[
692cfeb]:ardatan/graphql-tools (@graphql-tools/json-file-loader)
v8.0.25Compare Source
Patch Changes
[
2118a80]:v8.0.24Compare Source
Patch Changes
[
2fe123a]:v8.0.23Compare Source
Patch Changes
[
dddc5f6]:v8.0.22Compare Source
Patch Changes
[
fbb58b5]:v8.0.21Compare Source
Patch Changes
[
fd105f4,fded91e,3b99a9b]:ardatan/graphql-tools (@graphql-tools/load)
v8.1.7Compare Source
Patch Changes
[
2118a80]:v8.1.6Compare Source
Patch Changes
[
2fe123a]:v8.1.5Compare Source
Patch Changes
[
dddc5f6]:v8.1.4Compare Source
Patch Changes
[
fbb58b5]:v8.1.3Compare Source
Patch Changes
[
fd105f4,fded91e,3b99a9b]:ardatan/graphql-tools (@graphql-tools/merge)
v9.1.6Compare Source
Patch Changes
[
2118a80]:v9.1.5Compare Source
Patch Changes
[
2fe123a]:v9.1.4Compare Source
Patch Changes
[
dddc5f6]:v9.1.3Compare Source
Patch Changes
[
fbb58b5]:v9.1.2Compare Source
Patch Changes
[
fd105f4,fded91e,3b99a9b]:ardatan/graphql-tools (@graphql-tools/utils)
v10.11.0Compare Source
Minor Changes
#7588
2118a80Thanks @EmrysMyrddin! - Add optional schema coordinate in error
extensions. This extension allows to precisely identify the source of the error by automated tools
like tracing or monitoring.
This new feature is opt-in, you have to enable it using
schemaCoordinateInErrorsexecutoroption.
Caution: This feature, when enabled, will expose information about your schema. If you need to
keep your schema private and secret, you should strip this attribute at serialization time before
sending errors to the client.
v10.10.3Compare Source
Patch Changes
2fe123aThanks @ardatan! - Revert
#7683 which can cause unexpected breaking changes so
as before the schema extension node will always be converted to a schema definition node
v10.10.2Compare Source
Patch Changes
#7679
dddc5f6Thanks @ardatan! - Support "federation/subgraph style" schemas in
astFromSchemaandprintSchemaWithDirectivesIf a
GraphQLSchemadoesn't have any defined operation types, we should print the schemadefinition as an extension rather than omitting it entirely. They are not a valid schema on their
own, but they are valid subgraph schemas in a federation setup, and it is possible to build such
schemas with
assumeValidoptions.v10.10.1Compare Source
Patch Changes
fbb58b5Thanks @ardatan! - Remove `dset` dependency
v10.10.0Compare Source
Minor Changes
#5269
fded91eThanks @uroslates! - Add default values to the arguments
When the schema is like following;
The generated operation will be like following;
Patch Changes
#7012
fd105f4Thanks @ardatan! - Fix the bug in
mergeDeep;The following inputs and outputs are corrected;
mergeDeep([{a:2}, undefined])- Any nullish values should be ignored so it should return{a:2}mergeDeep([])- no sources should returnundefinedmergeDeep([undefined])- no sources should returnundefined#5294
3b99a9bThanks @n1ru4l! - Do not map builtin scalars
Configuration
📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Warsaw, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.