-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(compose/hoist-field): create new field if the target does not exist #7676
Conversation
The build artifacts of |
Apollo Federation Subgraph Compatibility Results
Learn more: |
The build artifacts of |
💻 Website PreviewThe latest changes are available as preview in: https://f071b885.graphql-mesh.pages.dev |
The build artifacts of |
The latest changes of this PR are not available as |
The build artifacts of |
Make sure you have updated both. Otherwise, could you create a new issue with a reproduction? |
This bug is with Prefix ... so new issue. Thanks |
If the target hoisted field is a new field name that doesn't exist, create that field and keep the
existing one;
type Query { users(limit: Int!, page: Int): UserSearchResult # Keep this + usersResults(limit: Int!, page: Int): [User!]! # Add a new one } scalar _HoistConfig type UserSearchResult { page: Int! } type User { id: ID! name: String! }