Discussion: some OAS Enhancer additions for discussion #4539
Conversation
|
Some of theese "x-..." and "title" properties are used by different sdk generators to generate frontend code. Removing this stuff might break frontend code generation. |
I understand that title can be used, that was tentatively added. Do you have any practical examples for use of the The consolidator could be the only core worthy addition. |
add security enhancer to add default security scheme impl. loopbackio#4386 Signed-off-by: Douglas McConnachie <[email protected]>
make rest server getApiSpec method async Signed-off-by: Douglas McConnachie <[email protected]>
add openapi spec enhancer to rest server with security enhancer by default impl. loopbackio#4365 Signed-off-by: Douglas McConnachie <[email protected]>
Add openapi schema enhancer to consolidate entire openapi schema Schema enhancer added to openapi-v3 package, utilised in rest server. Creates references to schema to reduce duplication. Signed-off-by: Douglas McConnachie <[email protected]>
add example enhancers Signed-off-by: Douglas McConnachie <[email protected]>
dougal83
force-pushed
the
enhancer-additions
branch
from
32c5f59 to
71efa98
Compare
|
Closed. Move discussion to issue later. |
I've put together some OAS Enhancer additions for discussion if any are of interest to create a PR. I'm just looking at tidying the output, removing unnecessary spec pollution, reorder in a way that I see as more logical and others, see commits.
(Core in bold, others could be optional community addons)
Can look at others on suggestion. Might need @jannyHou to help integrate properly on rest server. :)
Please take a look at the resultant openapi.json spec from these enhancers.