This repository has been archived by the owner on Nov 20, 2022. It is now read-only.
fix(deps): update dependency @graphql-tools/load to v7.7.7 #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/koenverburg/koenverburg-dev/12mmx5mruThskz6gYeB8UAL4DkdA [Deployment for 93fef65 failed] |
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
64a07dd
to
d63999b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
d63999b
to
ac60563
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
ac60563
to
4f81f7f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
4f81f7f
to
93fef65
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
93fef65
to
2713cc4
Compare
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
2713cc4
to
6033003
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
6033003
to
2d4e5d0
Compare
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
2d4e5d0
to
1480519
Compare
renovate
bot
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
7.4.1->7.7.7Release Notes
ardatan/graphql-tools
v7.7.7Compare Source
Patch Changes
43c736bd]:v7.7.6Compare Source
Patch Changes
71cb4fae,403ed450]:v7.7.5Compare Source
Patch Changes
4fe3d9c0]:v7.7.4Compare Source
Patch Changes
2609d71f]:v7.7.3Compare Source
Patch Changes
821ef03cThanks @ardatan! - Fix import for ESM supportv7.7.2Compare Source
Patch Changes
#4624
e3167edcThanks @n1ru4l! - Fix CommonJS TypeScript resolution withmoduleResolutionnode16ornodenextUpdated dependencies [
8cc8721f,e3167edc]:v7.7.1Compare Source
Patch Changes
2a3b45e]v7.7.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v7.6.0Compare Source
Minor Changes
4914970:mergeSchemaswas skippingdefaultFieldResolveranddefaultMergedResolverby 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 newincludeDefaultMergedResolverflag is introduced ingetResolversFromSchemato put default "proxy" resolvers in the extracted resolver map formergeSchemas.This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing
defaultMergedResolverin the final merged schema which should come from the wrapped schema.Patch Changes
4914970: No longer callmergeSchemasif a single schema is loaded.Previously all typeDefs and resolvers were extracted and the schema was rebuilt from scratch.
But this is not necessary if there is only one schema loaded with
loadSchema4914970]v7.5.14Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v7.5.13Compare Source
Patch Changes
da7ad43]v7.5.12Compare Source
Patch Changes
c0762ee]v7.5.11Compare Source
Patch Changes
0fc510c]v7.5.10Compare Source
Patch Changes
31a33e2]v7.5.9Compare Source
Patch Changes
cb23887]v7.5.8Compare Source
Patch Changes
0bbb176]v7.5.7Compare Source
Patch Changes
904c084]v7.5.6Compare Source
Patch Changes
722abad]v7.5.5Compare Source
Patch Changes
be2c02d]v7.5.4Compare Source
Patch Changes
d36d530]v7.5.3Compare Source
Patch Changes
0c0c685: fix - align versions0c0c685]v7.5.2Compare Source
Patch Changes
1834136: feat(visitResult): ignore if field not present in visited object1834136]v7.5.1Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v7.5.0Compare Source
Minor Changes
b107413: feat(load): support custom require for custom loadersPatch Changes
7b5d72c]Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.