Subgraph doesn't work

[Brilhante29]

When I run my project with subgraphs in the latest version of node and nestjs, I got this error

super(
^
GraphQLError: The schema is not a valid GraphQL schema.. Caused by:
Invalid definition for directive "@tag": "@tag" should have locations FIELD_DEFINITION, OBJECT, INTERFACE, UNION, ARGUMENT_DEFINITION, SCALAR, ENUM, ENUM_VALUE, INPUT_OBJECT, INPUT_FIELD_DEFINITION, but found (non-subset) FIELD_DEFINITION, OBJECT, INTERFACE, UNION, ARGUMENT_DEFINITION, SCALAR, ENUM, ENUM_VALUE, INPUT_OBJECT, INPUT_FIELD_DEFINITION, SCHEMA

[TLadd]

I experienced the same error going from 2.2.3 -> 2.3.0 using pothos as my schema builder.

[saevarb]

I also just ran into this same issue when going from 2.0.5 to 2.3.0. In particular, this happens when calling builder.toSubgraphSchema. The primary motivation for this upgrade was getting support for node 18, but it seems e.g. 2.2.3 is fine for my use case for now.

[Brilhante29]

with 2.2.3 works perfectly?

[alexbchr]

Same problem here with 2.3.0 and 2.3.1. No issue with 2.2.3

[sachindshinde]

From what we can tell, this error occurs for subgraphs when they're using the @tag directive definition from federation spec version 2.3, i.e.

directive @tag(name: String!) repeatable on
  | FIELD_DEFINITION
  | INTERFACE
  | OBJECT
  | UNION
  | ARGUMENT_DEFINITION
  | SCALAR
  | ENUM
  | ENUM_VALUE
  | INPUT_OBJECT
  | INPUT_FIELD_DEFINITION 
  | SCHEMA

but if their subgraph schema is declaring a lower federation spec, e.g.

extend schema @link(url: "https://specs.apollo.dev/federation/v2.2", ...)

You'll need to either upgrade your subgraph to use federation spec v2.3 e.g. with

extend schema @link(url: "https://specs.apollo.dev/federation/v2.3", ...)

or you'll need to use the @tag directive definition of your declared federation spec version (or alternatively omit the @tag directive definition if possible, as buildSubgraphSchema() should automatically add the appropriate definition).

[zhumeisongsong]

With 2.2.3 works perfectly.

[marc-wilson]

Still in issue in 2.9.3. After downgrading to 2.2.3 it worked.

Any update on when we can expect a fix?