Replies: 1 comment
-
From looking at https://github.com/completecoding/serverless-auto-swagger/blob/8e3fae93109c9c2a8b7d76eb1779702d774e6c8d/src/ServerlessAutoSwagger.ts#L119C3-L134C5 it seems that my expectation of how merging should work is correct, it's just not doing what I expected From poking around, it seems the issue stems from |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been trying to wrap my head around how to go about
(as indicated in the README)
The way I understand it, this won't be something done in the the
serverless.yaml
. file, but rather on the swagger json files.Assuming that interpretation is correct, now the question is "how to do this in a way that isn't overwrritten by subsequent auto generations of the docs?"
I initially thought it was through the
swaggerFiles
attribute, where I'd provide additional definitions for a route and the auto generation would merge that with the info derived from theserverless.yaml
However, that didn't work (see configuration below).
The generated
swagger.js
file only considers what's in theserverless
. What's the correct way to extend the definitions in the serverless to ensure proper maintainability of the docs?For instance
Beta Was this translation helpful? Give feedback.
All reactions