Vite · API Governance Rules
Vite API Rules
Spectral linting rules defining API design standards and conventions for Vite.
9 Rules
error 4
warn 5
Rule Categories
vite
Rules
warn
vite-operation-ids-camel-case
Operation IDs must use camelCase to match Vite's JavaScript API naming conventions.
$.paths[*][*].operationId
warn
vite-paths-must-have-tags
All operations must be tagged for proper documentation grouping.
$.paths[*][*]
error
vite-require-operation-summaries
All operations must have a human-readable summary.
$.paths[*][*]
warn
vite-require-descriptions
All operations, schemas, and parameters must have descriptions for developer clarity.
$.paths[*][*]$.components.schemas[*]$.paths[*][*].parameters[*]
error
vite-server-paths-start-with-slash
All paths must start with a forward slash.
$.paths
warn
vite-schema-properties-have-types
All schema properties must define an explicit type for TypeScript interoperability.
$.components.schemas[*].properties[*]
error
vite-use-openapi-31
Vite API specs must use OpenAPI 3.1.0 to leverage full JSON Schema support.
$
warn
vite-info-contact-required
API info must include contact information pointing to the Vite team.
$.info
error
vite-responses-have-200
GET operations must always define a 200 success response.
$.paths[*].get