Replies: 1 comment 6 replies
-
both approaches have its own benefits, but I believe separating it out to yaml will be a lot cleaner along with some process in CI to make sure, for new endpoints there is an entry in yaml, may be we should make a consistent pattern and follow it across the suite, be it mvc or webflux or node/express or fastapi .... |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello friends! I've been talking with @annibalsilva about the Swagger documentation style and now I would like to include more opinions on that.
Based on this PR, on SPAR Oracle API, was decided to go with
Annotated
style instead of ayaml
orjson
file. Adding annotations to all resources, methods, and parameters. However, this way makes the code a bit hard to read, making it quite polluted.So I want to ask you, what are your opinions on that, and if BC Gov has some definition regarding these two options.
As a matter of comparison, I opened a PR using the
yaml
file, see it here and the file herecc: @mishraomp @paulushcgcj @annibalsilva @DerekRoberts @ConradBoydElliottGustafson
Beta Was this translation helpful? Give feedback.
All reactions