Repeatable directives

At a glance

• Identifier: #472
• Stage: RFC 3 / Accepted
• Champion: @OlegIlyenko
• Latest activity: 2 commits pushed on 2020-01-10
• Spec PR: https://github.com/graphql/graphql-spec/pull/472

Spec PR description

This proposal directly relates to a discussion in https://github.com/facebook/graphql/issues/429. As was discussed at the latest WG meeting, I'm creating several alternative proposals. This one implements proposed solution 4. Limit the validation to only these directives that are explicitly marked as "unique". This implies that we need to introduce a new option in the directive definition.

It limits the scope of "Directives Are Unique Per Location" to directives that are explicitly marked as unique.

This proposal is mutually exclusive with other alternative proposals:

• [RFC] Limit uniqueness to @skip, @include and @deprecated directives (#471)
• [RFC] Limit directive uniqueness to explicitly marked directives (#472, this one)

@leebyron @IvanGoncharov @jjergus I would appreciate your reviews.

Closes #429 Closes #471

Timeline

• 2 commits pushed on 2020-01-10:
  • leebyron committed "Apply suggestions from code review"
  • leebyron committed "Editorial"
• Added to WG agenda on 2019-10-10
• Mentioned in WG notes on 2019-10-10
• Commit pushed on 2018-10-08 by OlegIlyenko: Improved repeatable directive description
• 2 commits pushed on 2018-10-05:
  • OlegIlyenko committed "Improved repeatable directive example"
  • OlegIlyenko committed "Better description for `repeatable` directives"
• Commit pushed on 2018-10-04 by OlegIlyenko: Rename repeatable → isRepeatable in the introspection
• Commit pushed on 2018-10-02 by OlegIlyenko: Use repeatable instead of unique keyword. Also changed the default.
• Commit pushed on 2018-06-25 by OlegIlyenko: Mark @skip. @include and @deprecated as unique
• Spec PR created on 2018-06-24 by OlegIlyenko
• Commit pushed on 2018-06-24 by OlegIlyenko: Limit directive uniqueness to explicitly marked directives