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
| missing_path_parameter | For a path that contains path parameters, flag any operations that do not correctly define those parameters. | shared |
207
207
| snake_case_only | Flag any path segment that does not use snake case. | shared |
208
+
| paths_case_convention | Flag any path segment that does not follow a given case convention. snake_case_only must be 'off' to use. | shared |
208
209
209
210
##### [responses][4]
210
211
| Rule | Description | Spec |
@@ -222,6 +223,8 @@ The supported rules are described below:
222
223
| no_property_description | Flag any schema that contains a 'property' without a `description` field. | shared |
223
224
| description_mentions_json | Flag any schema with a 'property' description that mentions the word 'JSON'. | shared |
224
225
| array_of_arrays | Flag any schema with a 'property' of type `array` with items of type `array`. | shared |
226
+
| property_case_convention | Flag any property with a `name` that does not follow a given case convention. snake_case_only must be 'off' to use. | shared |
227
+
| enum_case_convention | Flag any enum with a `value` that does not follow a given case convention. snake_case_only must be 'off' to use. | shared |
225
228
226
229
##### security_definitions
227
230
| Rule | Description | Spec |
@@ -265,9 +268,11 @@ For rules that accept additional configuration, there will be a limited set of a
0 commit comments