Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
feat(booter-lb3app): process generated OpenApiSpec of lb3 app #3623
While migration from lb3 to lb4 I had several issues with the converted openapi spec of my lb3app, e.g.:
We solved this by post processing the generated openapi spec before it gets published into lb4.
@derdeka Thank you for the patch!
Do these fixes apply to most use cases? If so, we should fix them in the booter implementation itself.
I'm open to the idea to allow
Please add some tests.
Thank you @derdeka for the pull request.
I agree with what Raymond wrote above - it would be best to fix the code that's generating OpenAPI spec, so that no further post-processing is needed. It makes me wonder - are you using Swagger with your LB3 application? Is that swagger spec correct?
I am not sure how easy would be to support this use case at loopback-swagger and/or the booter level. Your proposal to allow applications to contribute a custom post-processing function (handler) looks like a great solution
Can we find a shorter name for