Teledyne Technologies · API Governance Rules
Teledyne Technologies API Rules
Spectral linting rules defining API design standards and conventions for Teledyne Technologies.
10 Rules
error 3
warn 6
Rule Categories
teledyne
Rules
warn
teledyne-operation-ids-camel-case
Operation IDs must use camelCase naming convention.
$.paths[*][*].operationId
error
teledyne-operations-have-summaries
All operations must have a summary.
$.paths[*][*]
warn
teledyne-title-case-summaries
Operation summaries must use Title Case.
$.paths[*][*].summary
warn
teledyne-operations-have-tags
All operations must be tagged.
$.paths[*][*]
error
teledyne-responses-have-descriptions
All responses must have descriptions.
$.paths[*][*].responses[*]
error
teledyne-servers-defined
API must define at least one server.
$
warn
teledyne-path-parameters-described
All path parameters must have descriptions.
$.paths[*][*].parameters[?(@.in === 'path')]
warn
teledyne-json-responses-defined
JSON-returning endpoints must define response schemas.
$.paths[*][*].responses[200].content.application/json
hint
teledyne-temp-unit-enum
Temperature unit parameters should use standard C/F/K enum.
$.paths[*][*].parameters[?(@.name === 'tempUnit')]
warn
teledyne-components-schemas
API must define reusable schemas.
$.components