Apache HttpComponents · API Governance Rules
Apache HttpComponents API Rules
Spectral linting rules defining API design standards and conventions for Apache HttpComponents.
13 Rules
error 3
warn 8
info 2
Rule Categories
http
no
operationid
schema
servers
Rules
error
http-client-operation-summary
All Apache HttpComponents API operations must have a summary
$.paths[*][get,put,post,delete,patch]
error
http-client-operation-id
All Apache HttpComponents API operations must have an operationId
$.paths[*][get,put,post,delete,patch]
warn
http-client-operation-tags
All Apache HttpComponents API operations must have at least one tag
$.paths[*][get,put,post,delete,patch]
warn
http-client-schema-description
All Apache HttpComponents schema components must have a description
$.components.schemas[*]
info
http-client-property-description
All Apache HttpComponents schema properties should have descriptions
$.components.schemas[*].properties[*]
warn
http-client-info-contact
API info must include contact information
$.info
warn
http-client-info-license
API info must include license information
$.info
error
servers-https-only
Server URLs must use HTTPS.
$.servers[*].url
warn
servers-expected-domain
Server URLs should be on the example.com domain.
$.servers[*].url
warn
operationid-casing
Operation IDs should be camelCase (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].operationId
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
info
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
no-empty-descriptions
Descriptions must not be empty strings.
$..description