-
Notifications
You must be signed in to change notification settings - Fork 275
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: make test supergraphs valid #6084
Conversation
this becomes a problem when switching to the native QP by default
@lennyburdette, please consider creating a changeset entry in |
CI performance tests
|
I think it's a little suspicious that Rust doesn't accept those. Could there be customers with such "incomplete" supergraphs? will discuss with the QP team if we shouldn't change the native QP instead |
the contract we have with customers is that they should use only federation composition to generate supergraphs — i don't think we need to relax our supergraph validation because our own composition could must always emit valid supergraphs. whether we should, maybe to adhere to the robustness principle, might be a discussion worth having, but i'm not sure. |
Right. I guess we would've also known by now if any customer does rely on it through all the testing we've done with Rust. |
✅ Docs Preview ReadyConfiguration{
"repoOverrides": {
"apollographql/router@dev": {
"remote": {
"owner": "apollographql",
"repo": "router",
"branch": "lb/fix-supergraphs"
}
}
}
}
2 pages published. Build will be available for 30 days. |
this becomes a problem when switching to the native QP by default
Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Note any exceptions here
Notes
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩