Chick-fil-A · API Governance Rules
Chick-fil-A API Rules
Spectral linting rules defining API design standards and conventions for Chick-fil-A.
32 Rules
error 5
warn 17
info 10
Rule Categories
get
global
info
openapi
operation
parameter
paths
request
response
schema
server
servers
tag
Rules
warn
info-title-prefix
API title should start with "Chick-fil-A".
$.info.title
warn
info-description-required
Info object must have a description of reasonable length.
$.info
error
info-version-required
Info object must declare a version.
$.info
info
info-contact-required
Info object should declare a contact.
$.info
warn
openapi-version-3
Specifications must use OpenAPI 3.0.x.
$.openapi
error
servers-defined
At least one server must be defined.
$.servers
warn
server-https
Server URLs should use HTTPS.
$.servers[*].url
info
server-description
Each server should have a description.
$.servers[*]
warn
paths-no-trailing-slash
Paths must not end with a trailing slash.
$.paths[*]~
error
paths-no-query-string
Paths must not contain query strings.
$.paths[*]~
info
paths-lower-case
Path segments should be lower camelCase or kebab-case (no UPPER snake).
$.paths[*]~
error
operation-operationId-required
Every operation must declare an operationId.
$.paths[*][get,post,put,patch,delete]
warn
operation-operationId-camelcase-verb
operationId should be camelCase and begin with a verb (get/list/add/run/create/update/delete).
$.paths[*][get,post,put,patch,delete].operationId
warn
operation-summary-required
Every operation must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-prefix
Operation summaries should be prefixed with "Chick-fil-A".
$.paths[*][get,post,put,patch,delete].summary
warn
operation-description-required
Every operation should have a description.
$.paths[*][get,post,put,patch,delete]
warn
operation-tags-required
Every operation must declare at least one tag.
$.paths[*][get,post,put,patch,delete]
info
operation-microcks-extension
Each operation should carry an x-microcks-operation extension for mock compatibility.
$.paths[*][get,post,put,patch,delete]
info
global-tags-defined
A global tags array should be defined.
$
info
tag-description
Each global tag should have a description.
$.tags[*]
warn
tag-title-case
Tag names should be Title Case (single capitalized words like "Accounts", "Networking").
$.tags[*].name
warn
parameter-description-required
Every parameter must have a description.
$..parameters[*]
warn
parameter-schema-required
Every parameter must declare a schema with a type.
$..parameters[?(@.in)]
warn
request-body-json
Request bodies should offer application/json content.
$.paths[*][post,put,patch].requestBody.content
info
request-body-description
Request bodies should have a description.
$.paths[*][post,put,patch].requestBody
warn
response-success-defined
Operations must define a 200 (or other 2xx) success response.
$.paths[*][get,post,put,patch,delete].responses
warn
response-description-required
Every response must have a description.
$.paths[*][get,post,put,patch,delete].responses[*]
info
response-json-content
2xx responses should return application/json.
$.paths[*][get,post,put,patch,delete].responses.200.content
warn
schema-description-required
Top-level component schemas should have a description.
$.components.schemas[*]
info
schema-property-type
Schema properties should declare a type.
$.components.schemas[*].properties[*]
info
schema-property-example
Scalar schema properties should include an example.
$.components.schemas[*].properties[?(@.type && @.type != 'object' && @.type != 'array')]
error
get-no-request-body
GET operations must not declare a request body.
$.paths[*].get