Closed benjie closed 2 weeks ago
Name | Link |
---|---|
Latest commit | 73e216650a6938fe02df0f2680d61527705327c2 |
Latest deploy log | https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/667565064feae80008d4d3d7 |
Deploy Preview | https://deploy-preview-4118--compassionate-pike-271cb3.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Hi @benjie, I'm @github-actions bot happy to help you with this PR π
The GraphQL specification mandates certain validation rules that all compliant GraphQL services must implement. Beyond these, services are free to add their own validation rules. The TSC has been discussing the idea of "recommended" validation rules for some time, rules that are not mandatory for compliance but are recommended to enhance the resilience of GraphQL schemas.
@enisdenjo has developed a new validation rule to limit introspection query depth; the TSC saw this as an excellent opportunity to introduce the new "recommended" validation rules system.
This PR introduces a new
recommendedRules
export to contain these recommended rules, starting with Denis' rule. To ensure seamless integration we are merging theserecommendedRules
into the existingspecifiedRules
export, which acts as the default list of validation rules (we may adjust this approach in a future major release, possibly by exposing adefaultRules
export, but for now we aim to ease adoption).Services can opt-out of the recommended rules by creating their own rules list without them:
We anticipate adding to these recommended rules over time and iterating them based on community feedback. Ultimately they may become recommended as part of the official specification, or be removed from the defaults.