Introduce @requiresScopes directive in composition

[trevor-scheer]

Effectively duplicated and adapted work from #2644

This PR introduces the new @requiresScopes directive for composition

With this change, users can now compose @requiresScopes applications from their subgraphs into a supergraph. This addition will support a future version of Apollo Router that enables authenticated access to specific types and fields via directive applications.

Since the implementation of @requiresScopes is strictly a composition and execution concern, there's no change to the query planner with this work. The execution work is well under way in Apollo Router (and won't be built at all for Gateway). So as far as this repo is concerned, only composition is concerned with @requiresScopes.

TODO:

• changelog entry (pending some internal feedback)
• possibly some more interesting test cases
• pending discussion on use of custom Scope scalar for input type

[changeset-bot]

🦋 Changeset detected

Latest commit: b360a78

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@apollo/query-planner	Minor
@apollo/composition	Minor
@apollo/federation-internals	Minor
@apollo/gateway	Minor
@apollo/query-graphs	Minor
@apollo/subgraph	Minor
apollo-federation-integration-testsuite	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[pcmanus]

Had a look, and currently lgtm. Holding off on approving until this get out of "draft" and we've dealt with the few remaining TODO, but so far so good.

[clenfest]

I may have missed a conversation on this, but did we want to have two separate specs or a single spec for this?

[clenfest]

Oh, one thing that I remembered. Could you add both directives into the directivesComposedByDefault array on line 172 of composeDirectiveManager.ts? It will prevent people from trying to manually promote those directives to the supergraph.

[clenfest]

looks good

[clenfest]

RegisterSubFeature should probably take the whole FeatureDefinitions[] and the federation version, then it can figure out what version is needed based on the minimumFederationVersion specified. That we don't have to have the federationSpec know anything about the version relationships and can get rid of all of these if version statements.

[trevor-scheer]

I don't disagree with the ergonomic benefit, but there's a bit to untangle underneath that I'd rather punt on.

[trevor-scheer]

@clenfest approved this in Slack and I'd like to get this on next today so we can kick off a harness run.