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 }}
Repository navigation
Commit d206de6
Browse filesBrowse the repository at this point in the historyBrowse files
Apply directives declared on the schema and its extensions
Directives on `schema @foo { ... }` and `extend schema @foo` were never
read, so e.g. Apollo Federation v2's `extend schema @link(...)` was
missing from the GraphQLSchema and from federation-jvm's _service.sdl.
They're now added as schema applied directives, the schema definition's
first, then its extensions'.
RootTypeInfo also took the last SchemaDefinition, which can be an
extension, so `schema { query: MyQuery }` followed by `extend schema @foo`
lost the custom root type. Operation types are now merged across the
definition and its extensions.
Only applied directives are set on the schema: graphql-java doesn't
resolve type references in the deprecated legacy schema directives, so
an enum argument would fail validation.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
0 commit comments