We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 459280e commit f21d6ceCopy full SHA for f21d6ce
docs/checks.md
@@ -18,6 +18,15 @@ consistent, we use a standard set of terms.
18
19
## Technical Requirements
20
21
+Checks can be rather cumbersome, particularly in large volumes. To combat this,
22
+we have devised a set of implementation requirements:
23
+
24
+- Checks with more than 150 entries should be batched into chunks of 150
25
+- Checks with more than 50 entries should have their contents factored out into
26
+ a separate file, formatted as a CSV and bearing the same name as the last
27
+ element of the check path. For example, `cliches.misc.write_good` has the
28
+ associated file `write-good`
29
30
## Suitability
31
32
It is difficult to ensure Proselint's catalog of checks remains both tidy and
0 commit comments