You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.
/// <summary>
/// Apollo Federation v2 base schema object that allows users to apply custom schema directives (e.g. @composeDirective)
/// </summary>
[Link("https://specs.apollo.dev/federation/v2.5", new string[] {
"@composeDirective",
"@extends",
"@external",
"@key",
"@inaccessible",
"@interfaceObject",
"@override",
"@provides",
"@requires",
"@shareable",
"@tag",
"FieldSet"
})]
Since the schema version is specified per variant in Apollo Studio, can we get this to be an argument to the .AddApolloFederationV2() method? For example, right now we're running Router 1.19.0 which only supports Fed v2.4, so being able to specify something like the below would be helpful:
Hello 👋
I've updated FederatedSchema to accept federation version parameter (#23). Ideally we should support full @link capabilities (#24) but that is a much bigger change....
We're getting the following ever from Rover when trying to publish to a variant that supports Federation v2.4:
Looks like the Federation version is hardcoded into the URL @ https://github.com/apollographql/federation-hotchocolate/blob/main/src/Federation/Two/FederatedSchema.cs#L10:
Since the schema version is specified per variant in Apollo Studio, can we get this to be an argument to the
.AddApolloFederationV2()
method? For example, right now we're running Router 1.19.0 which only supports Fed v2.4, so being able to specify something like the below would be helpful:Thoughts?
The text was updated successfully, but these errors were encountered: