Add validation rules to check for deprecated fields #389
Comments
|
Shouldn't bee hard according to @leebyron: |
|
@0xR if you do it, make sure it's not part of specified rules, because those will make the query fail by default. It should be an optional rule that people can import. |
|
Should be really easy to copy this rule and modify it a bit: https://github.com/graphql/graphql-js/blob/master/src/validation/rules/FieldsOnCorrectType.js |
leebyron
added a commit
that referenced
this issue
Jan 19, 2017
This adds a utility for finding field and enum deprecation usages. The function signature is very similar to validation which should make using it easy where validation is already being used in a reporting flow. Closes #389
Merged
leebyron
added a commit
that referenced
this issue
Jan 19, 2017
This adds a utility for finding field and enum deprecation usages. The function signature is very similar to validation which should make using it easy where validation is already being used in a reporting flow. Closes #389
leebyron
added a commit
that referenced
this issue
Jan 19, 2017
This adds a utility for finding field and enum deprecation usages. The function signature is very similar to validation which should make using it easy where validation is already being used in a reporting flow. Closes #389
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The same way this package includes a validation rule to check for unknown fields, it might be valuable to be able to check for deprecated fields as well.
The text was updated successfully, but these errors were encountered: