Formant · API Governance Rules
Formant API Rules
Spectral linting rules defining API design standards and conventions for Formant.
5 Rules
warn 4
info 1
Rule Categories
formant
Rules
warn
formant-operation-ids-dot-notation
Formant uses . as operationId convention.
$.paths[*][*].operationId
warn
formant-uuid-format
All Formant resource identifier fields (organizationId, deviceId, id, etc.) must be typed as string with format uuid.
$.components.schemas[*].properties[?(@property.match(/Id$/) || @property === 'id')]
warn
formant-bearer-auth-required
All Formant API paths except /admin/auth/login must declare bearerAuth security.
$.paths[?(@property !== '/admin/auth/login')][*]
warn
formant-responses-have-descriptions
Formant API responses should all carry a description field for clarity.
$.paths[*][*].responses[*]
info
formant-stream-type-enum
Formant stream types are a fixed vocabulary: bitset, localization, point cloud, location, file, health, transform tree, battery, video, numeric set, json, image, numeric, text.
$.components.schemas[*].properties.type