`@inaccessible` test is inconsistent with specification. about apollo-federation-subgraph-compatibility

[ddebrunner]

Thanks, that clears it up!

[prasek]

@ddebrunner the @inaccessible spec you're looking at is for supergraph usage & is enforced at runtime in the supergraph Gateway/Router. The processor implementing @inaccessible is the Gateway/Router.

Usage of @inaccessible in subgraphs hasn't been added to the subgraph spec yet, and it's used in the subgraph as a compose-only directive, that is directly composed/merged into the supergraph schema during composition, and only enforced by a processor in the Gateway. This is typically done for internal routing keys that need be used for cross-subgraph joins but where that internal routing key should not be present in the public API schema that clients see when interacting with a supergraph endpoint.

We'll add the subgraph spec docs for @inaccessible and make this supergraph vs. subgraph distinction more clear. appreciate you calling this out. 🙏

from the https://github.com/apollographql/apollo-federation-subgraph-compatibility#testing-spec-compliance

@inaccessible (in subgraphs)

Must be seen as a valid schema directive in the subgraph library service sdl. Is verified by checking for its inclusion in the query { _service { sdl } } result. Must also be able to query inaccessible fields from the Products schema.