SourceForge · API Governance Rules
SourceForge API Rules
Spectral linting rules defining API design standards and conventions for SourceForge.
12 Rules
error 4
warn 7
info 1
Rule Categories
sourceforge
Rules
error
sourceforge-rest-prefix
All SourceForge API paths must begin with /rest/
$.paths
warn
sourceforge-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][get,post,put,patch,delete].summary
error
sourceforge-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
sourceforge-operation-id-camel-case
OperationId must use camelCase convention
$.paths[*][get,post,put,patch,delete].operationId
warn
sourceforge-operation-has-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
sourceforge-post-has-request-body
POST operations must define a requestBody
$.paths[*].post
warn
sourceforge-401-response
Operations must document 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
warn
sourceforge-delete-returns-204
DELETE operations should return 204 No Content
$.paths[*].delete.responses
warn
sourceforge-tags-title-case
All tags in the spec must use Title Case
$.tags[*].name
error
sourceforge-security-defined
OAuth2 security must be defined globally or per operation
$
info
sourceforge-project-parameter
Project-scoped paths must use {project} path parameter
$.paths['/rest/p/{project}']
warn
sourceforge-response-schema-defined
Successful responses must have a schema
$.paths[*][get,post].responses['200','201'].content['application/json']