Stitching a remote GQL service does not expose directives

[MassiCav]

I am trying, using the 'stitching' pattern, to integrate a remote GQL service that is supposed to manage only the 'query' part of the logic. The remote service exposes 3 directives (limit, offset, order).

Using 'introspectSchema' and and 'executor' based on 'cross-undici-fetch' (as per documentation examples) I retrieve the remote schema definitions. When I print the introspection result done via the 'executor', I can see the 3 directives are part of the subschema.

After the subschema is stitched and passed to the Apollo server, the directives are not exposed in the final service.

What am I missing?

[ardatan]

This is a limitation in GraphQL specification. Introspection result doesn't have directives by its design. GraphQL Tools unfortunately have nothing to do with that. As a workaround you can add a query field _sdl to expose your full SDL.
See graphql/graphql-spec#300
and https://github.com/gmac/schema-stitching-handbook/tree/main/stitching-directives-sdl

[MassiCav]

Thank you for your prompt reply. What bothers me is that the introspection does not cancel the directives, it is the stitching function that does it.

Regarding the 'stitching-directives' pattern, the way I understood it at least, it uses directives to govern the stitching process; but the resulting gateway does not expose the directives present in the remote service