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
I wonder if there's a way to instruct schema renderer responsible for api.render attribute to use extend keywords on defined types instead of the @extends directive in the resulting SDL? Apollo docs seem to discourage use of the directive in favour of the keyword.
I.e. turning this:
typeQuery@extends { ... }
into this
extendtypeQuery { ... }
The text was updated successfully, but these errors were encountered:
coderfromhere
changed the title
Turning @GQLExtend to extend type instead of @extend
Turning @GQLExtend to extend type instead of @extendsDec 6, 2022
coderfromhere
changed the title
Turning @GQLExtend to extend type instead of @extends
Turning GQLExtend to extend type keywords instead of extends directive
Dec 6, 2022
FYI @extends directive/extend type syntax is no longer needed for Federation v2 and should generally be omitted from the schema. Extending types is still a useful functionality and there are valid use cases for it (but federation v2 does not require it all).
I Think we could handle this by moving GQLExtend into core and detecting it the way we do GQLDeprecated during derivation. Then we can just deprecate the one in the federation package.
Hi!
I wonder if there's a way to instruct schema renderer responsible for
api.render
attribute to useextend
keywords on defined types instead of the@extends
directive in the resulting SDL? Apollo docs seem to discourage use of the directive in favour of the keyword.I.e. turning this:
into this
The text was updated successfully, but these errors were encountered: