Update type definitions to expose AppliedDirectives. This initial implementation only exposes applied directive as metadata and does not modify runtime wiring to process them. Exposing directives is a pre-req to enable support for Apollo Federation (related: https://github.com/graphql-go/graphql/issues/492).
Following the pattern from graphql-java and HotChocolate where they make distinction between directive type definition (i.e. directive @foo on FIELD_DEFINITION, maps to existing Directive struct for backwards compatibility) and where directives are actually applied within the schema (i.e. type Foo @bar { baz @qux }, maps to new AppliedDirective struct`).
Coverage decreased (-0.4%) to 91.607% when pulling 0cd84ad8cb5a619dd32e41b3936db12a01f354a6 on dariuszkuc:applied_directives into 09272f35006712d597c0446258874ce7ff8919fb on graphql-go:master.
Update type definitions to expose
AppliedDirective
s. This initial implementation only exposes applied directive as metadata and does not modify runtime wiring to process them. Exposing directives is a pre-req to enable support for Apollo Federation (related: https://github.com/graphql-go/graphql/issues/492).Following the pattern from
graphql-java
andHotChocolate
where they make distinction between directive type definition (i.e.directive @foo on FIELD_DEFINITION
, maps to existingDirective struct
for backwards compatibility) and where directives are actually applied within the schema (i.e.type Foo @bar { baz @qux }
, maps to newAppliedDirective
struct`).