Next major version feature branch #10218
Draft
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
🦋 Changeset detectedLatest commit: 0b0c9bf The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
💻 Website PreviewThe latest changes are available as preview in: https://pr-10218.graphql-code-generator.pages.dev |
eddeee888
force-pushed
the
federation-fixes
branch
from
b3a8241 to
f5116a7
Compare
🚀 Snapshot Release (
|
| Package | Version | Info |
|---|---|---|
@graphql-codegen/cli |
5.0.6-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/core |
4.0.3-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/add |
5.0.4-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/fragment-matcher |
5.1.1-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/introspection |
4.0.4-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/schema-ast |
4.1.1-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/time |
5.0.2-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/visitor-plugin-common |
6.0.0-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript-document-nodes |
4.0.17-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/gql-tag-operations |
4.0.18-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript-operations |
4.6.1-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript-resolvers |
5.0.0-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typed-document-node |
5.1.2-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/typescript |
4.1.7-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/client-preset |
4.8.1-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/graphql-modules-preset |
4.0.17-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/testing |
3.0.5-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
@graphql-codegen/plugin-helpers |
6.0.0-alpha-20250329081240-1a64f6d2f211bdd3623a04b001a1dab8e0c92d3c |
npm ↗︎ unpkg ↗︎ |
eddeee888
force-pushed
the
federation-fixes
branch
from
aa191e7 to
dd2b0bd
Compare
eddeee888
changed the title
eddeee888
force-pushed
the
federation-fixes
branch
2 times, most recently
from
fd51b95 to
56fea45
Compare
… type for reference (#10216)
…face` entities, fix Interface types having non-meta resolver fields (#10221) * Add __resolveReference for applicable Interfaces - Deprecate generateInternalResolversIfNeeded.__resolveReference - Fix tests - Deprecate onlyResolveTypeForInterfaces - Add changeset - Cleanup - Handle __resolveReference generation in Interface - Let FieldDefinition decide whether to generate __resolveReference by checking whether parent has resolvable key * Fix test
…pes (of Interfaces) or Union members (#10283) * Implement logic to only generate __isTypeOf for implementing types OR union members * Remove unused types * Add changeset * Remove generateInternalResolversIfNeeded * Fix dev tests * Refactor to use parsedSchemaMeta
…esolversParentTypes instead of each resolver (#10297) * Bring reference selection set to ResolversParentTypes * Put back old types to extractReferenceSelectionSet * Update tests for TDD * Handle parent type consistently for __resolveReference and subsequent resolvers * Update tests
eddeee888
force-pushed
the
federation-fixes
branch
from
b0b7e86 to
0b0c9bf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related: #10206
__resolveReferenceto applicableInterfaceentities, fix Interface types having non-meta resolver fields #10221__isTypeofis only generated for implementing types (of Interfaces) or Union members #10283Breaking Changes
UnwrappedObjectutility type, as this was used to support the wrong previously generated type.onlyResolveTypeForInterfacesbecause majority of use cases cannot implement resolvers in Interfaces.generateInternalResolversIfNeeded.__resolveReferencebecause types do not have__resolveReferenceif they are not Federation entities or are not resolvable. Users should not have to manually set this option. This option was put in to wait for this major version.__isTypeOffor non-implementing-types or non-union-members@external,@providesand@key @keyscenarios easier