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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@graphql-tools/[email protected]
Minor Changes
#7310
692cfeb
Thanks @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#paths
aliasing 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.
@graphql-tools/[email protected]
Minor Changes
#7310
692cfeb
Thanks @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#paths
aliasing 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
]:@graphql-tools/[email protected]
Patch Changes
296b883
Thanks @dependabot! - dependencies updates:
[email protected]
↗︎(from
17.0.0
, independencies
)@graphql-tools/[email protected]
Patch Changes
[
692cfeb
]: