Open dkoeni opened 3 months ago
body request and response parameters in snake_case according to ISO 23029
summary must not an with an fullstop
naming conventions for tags
Use refs for parameters or schemas used multiple times
Adjust ordering of root objects to redocly conventions.
openapi: info: servers: security: tags: externalDocs: paths:
Reasoning:
We use 'redocly bundle' command to build complete OAS. Redocly reorders root object according to their conventions:
Adapt naming-conventions for parameters to OAS common practices
Most used practice is camelCase with 'Param'-Suffix:
parameters:
skipParam:
name: skip
in: query
description: number of items to skip
required: true
schema:
type: integer
format: int32
limitParam:
name: limit
in: query
description: max records to return
required: true
schema:
type: integer
format: int32
Summary tag must not stop with a full stop
Add identifier: Apache-2.0
(SPDX license expression) to License Object
pattern
must be of the following structure '^...$'
Please comment for new proposals of SFTI's naming conventions concerning the openAPI action / redocly workflow