Open danielkocot opened 3 years ago
Yes, it is not used. What would be your expectation?
extract the /api
part and add it as prefix to any endpoint path?
or (in case of Spring) put an @RequestMapping(path = "/api")
on the generated interfaces?
servers
allows multiple urls, we would need a way to tell the processor which one to pick:
servers:
- url: https://server-a/v1
- url: https://server-b/v1234
it is also possible to use variables in the url and define them as additional properties of the url
key. The example in the specification uses an enum for a variable, so it is possible to have multiple values. Makes sense, why use a variable if I have a single value only ;-)
servers:
- url: https://{var}.openapiprocessor.io:{port}/{path}
variables:
var: ...
port: ...
path: ...
Looking at the possibilities, it would work only for a subset of them. For example only single url and single value for a path
variable. Which would be ok for me. Hmm, maybe it would even work for more than a single url, I think the Spring annotation allows to configure multiple paths.
Questions over questions :-)
Yes, there are so many questions and possibilities. In my first reaction I wanted to put an annotation on generated interface. But now I added an annotation to the controller which implemented the api interface.
When I describe an API Spec
the base path will be ignored. I can't anything in the documentation.