Repeatable directives

At a glance

• Identifier: #472
• Stage: RFC3: Accepted
• Champion: @OlegIlyenko
• PR: Repeatable directives

Timeline

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

---

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