Skip to content

New Rule: Require "requiresScopes" directive on all object types #2907

Open
@spenserca

Description

@spenserca

Is your feature request related to a problem? Please describe.

We have run into issues where less experienced developers have not added scopes properly to their graph objects. This poses a security risk, and we are looking for a way to stop them from pushing insecure object types to our federated graph.

Describe the solution you'd like

I'd like to be able to run a schema validation check and have it fail if a subgraph is trying to push a change which includes a type that doesn't have the @requiresScopes directive applied.

Describe alternatives you've considered

Other options we've discussed are manual reviews of schema changes, but then our team becomes a bottleneck to all other teams pushing graph changes.

Additional context

This is a similar request as #2284 just with a different directive and scope

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      New Rule: Require "requiresScopes" directive on all object types · Issue #2907 · graphql-hive/graphql-eslint