You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the swagger spec generated from events does not create tags & operationid keys. Because of no tags the Swagger UI doesn't bring organised APIs. Because of no operationId, it is difficult to generate client for a swagger spec.
The Solution
Generate Swagger UI with tags and operationId
How to solve
For tags: either developer gives tags array in schema of event or calculate it from the id of the file. If none of this is present, then use ${method}_${endpoint} remove / from endpoint
For operationId: developer can give operationId, or id in the event shema. If none of this is present, then use the summary of the event to generate the id
The Problem
Currently the swagger spec generated from events does not create
tags
&operationid
keys. Because of no tags the Swagger UI doesn't bring organised APIs. Because of no operationId, it is difficult to generate client for a swagger spec.The Solution
Generate Swagger UI with tags and operationId
How to solve
For tags: either developer gives
tags
array in schema of event or calculate it from theid
of the file. If none of this is present, then use${method}_${endpoint}
remove/
from endpointFor operationId: developer can give
operationId
, orid
in the event shema. If none of this is present, then use thesummary
of the event to generate the idIn yamlLoader.ts add tags in every event
In core/router/Swagger.ts
Test Cases
Generated Swagger should have endpoints like this..
UI will look like this
The text was updated successfully, but these errors were encountered: