Whisky Hunter · API Governance Rules
Whisky Hunter API Rules
Spectral linting rules defining API design standards and conventions for Whisky Hunter.
9 Rules
error 2
warn 7
Rule Categories
whisky
Rules
warn
whisky-hunter-no-auth-required
The Whisky Hunter API is public and should not declare security requirements.
$.paths.*.*
warn
whisky-hunter-trailing-slash-paths
Whisky Hunter API paths end with a trailing slash per convention.
$.paths.*~
warn
whisky-hunter-format-query-param
GET endpoints should support the format query parameter for JSON output.
$.paths.*.get
error
whisky-hunter-response-200-defined
All GET operations must define a 200 response.
$.paths.*.get
warn
whisky-hunter-array-response-for-data-endpoints
Data endpoints should return arrays.
$.paths.*.get.responses.200.content.application/json.schema
warn
whisky-hunter-operation-ids-camel-case
All operationIds should use camelCase.
$.paths.*.*.operationId
error
whisky-hunter-tags-on-operations
All operations must have at least one tag.
$.paths.*.*
warn
whisky-hunter-description-on-operations
All operations should have a description.
$.paths.*.*
warn
whisky-hunter-slug-path-param
Distillery data path must use {slug} path parameter.
$.paths[?(@property.includes('distillery_data'))].get.parameters[*]