Pylons / Pylons/pyramid_openapi3
provide a way to load the openapi.yaml that doesn't server it at an endpoint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 84
- Forks
- 46
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 3
Description
Due to issues like https://github.com/Pylons/pyramid_openapi3/issues/104 I cannot define a yaml that fully matches the deployment environment so I'd prefer to just not serve the yaml if I can help it. I'd just like it to be used to validate paths, as the yaml defines everything relative to the app's subpath so works across deployments so long as pyramid_openapi3 is using request.application_url as the base path.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or implementation entry points; begin by tracing how pyramid_openapi3 loads and serves the openapi.yaml, including the request.application_url behavior described here. Done means the YAML remains available for path validation while its endpoint serving can be disabled, without breaking deployment-relative paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100