You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,7 @@ Each rule has emojis denoting:
24
24
|[known-type-names](rules/known-type-names.md)| A GraphQL document is only valid if referenced types (specifically variable definitions and fragment conditions) are defined by the type schema. | 🔮 ||
25
25
|[lone-anonymous-operation](rules/lone-anonymous-operation.md)| A GraphQL document is only valid if when it contains an anonymous operation (the query short-hand) that it contains only that one operation definition. | 🔮 ||
26
26
|[lone-schema-definition](rules/lone-schema-definition.md)| A GraphQL document is only valid if it contains only one schema definition. | 🔮 ||
27
+
|[match-document-filename](rules/match-document-filename.md)| This rule allows you to enforce that the file name should match the operation name | 🚀 ||
27
28
|[naming-convention](rules/naming-convention.md)| Require names to follow specified conventions. | 🚀 ||
28
29
|[no-anonymous-operations](rules/no-anonymous-operations.md)| Require name for your GraphQL operations. This is useful since most GraphQL client libraries are using the operation name for caching purposes. | 🚀 ||
0 commit comments