-
Notifications
You must be signed in to change notification settings - Fork 18
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 _service { sdl } render to hide federated fields #21
Comments
This was reverted in #29 and we need to look at taking a different approach |
Is there a version of the library that does render this properly? We're switching over from using a mesh server to using this library, and this is a serious blocker for us to deploy with. |
The SDL rendered with v0.2.4 is compliant with Gateway 2 and it works without any problems. We currently use it in production. The issue is about full compliance with Apollo Federation specs. Rendering these extra fields in the SDL doesn't affect the functionality as far as I can tell. To answer your question though, unfortunately, we do not have a version where this issue is fixed without introducing bugs like #47 or #28. |
While looking at this, I noticed that there might have been an update on Apollo Federation docs. It mentions:
https://www.apollographql.com/docs/federation/subgraphs/#query_service This may be implying that we don't need to omit federation-specific fields from the SDL render after all. Any thoughts @kdawgwilk? |
You are supposed to include the directives themselves on each field but it's the federated type definitions that are not recommended to be present eg |
|
@kzlsakal we could prob strip out those |
This PR will strip out the |
FYI federation v1 required SDL modifications to strip out the fed definitions but fed v2 accepts full schemas -> there is no need to filter anything so you could just print out whole schema. |
While implementing this PR apollographql/apollo-federation-subgraph-compatibility#35 I found we are not filtering federated schema fields from the SDL render like we should
The text was updated successfully, but these errors were encountered: