Neyts Zupan
Neyts Zupan
The idea is to ship pyramid_openapi3 with a custom JSON renderer, so that applications using pyramid_openapi3 (for example, the real-world-example-app) do not need to come up with their own custom...
I suppose, yes. I cannot know until I see it in action.
Where are the changes?
Ah yes, now I remember. The changes should be done here in this repo. And yes, tests need to pass before the PR can be merged :)
I haven't thought this through so this is coming from the top of my head: it seems it makes sense to have a `renderers.py` file in https://github.com/Pylons/pyramid_openapi3/blob/master/pyramid_openapi3/.
Maybe a good approach is to familiarize yourself with Pyramid, this tutorial is good: https://docs.pylonsproject.org/projects/pyramid/en/latest/quick_tutorial/
Should we instead raise an error in pyramid_openapi if we come up against a regex in view path? I'm a bit afraid of silently removing parts of the path, I...
Hey @Wim-De-Clercq, do you have any further thoughts on this?
> Fixing this issue would make the document and explorer usable - right now I have to hardcode into my openapi.yaml document that the server url is actually url: /prefix/api....
Does anything on https://swagger.io/docs/specification/api-host-and-base-path/ help? I'm eager to support your use case as long as we play by the OpenAPI specification rules.