openapi3-parser
openapi3-parser copied to clipboard
OpenAPI 3 parser to use a specification inside of the code in your projects
At the current moment changes merged into the Master branch could not trigger package version increment and it causes failed pipelines on Release tags created. Provide a mechanism to auto-update...
To be able to use another factory from other packages or to be able to extend the current package without code changes in 3rd party code we should use Protocols...
To be able to get the current path or schema name, we can consider passing somehow the whole path of a current Swagger node or other useful data.
Optimize current package structure: - [ ] SOLID directory structure - [ ] Code coverage and new tests - [ ] Tiny code refactoring and optimization - [ ] Introduce...
Since dataclasses have only immutable structure and could not be extended with different fields, we should turn slots parameter on. Example ```python from dataclasses import dataclasses @dataclass(slots=True) class Schema: ......
**What is a problem?** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] **Describe the solution you'd like** A clear and concise description...
add support for parsing "example" or "examples" as described [here](https://swagger.io/specification/#parameter-object): example Any Example of the parameter's potential value. The example SHOULD match the specified schema and encoding properties if present....
From https://github.com/manchenkoff/openapi3-parser/issues/28, add example/examples sections in result
**Describe the bug** A schema with recursive definition raised error **To Reproduce** Steps to reproduce the behavior: 1. Using sample schema as follow with recursive structure, allowed by spec: `...
**What is a problem?** Pypi homepage is quite too simple: https://pypi.org/project/openapi3-parser/ **Describe the solution you'd like** More description about project, how to install, source to github etc