A tool to convert an OpenAPI spec to an OMG spec
Project description
Assumptions
- If there are multiple content types available for a given path, the content type
application/jsonshall be preferred if available. Ifapplication/jsonis not available, then an appropriate content type will be chosen arbitrarily - OMG doesn't support multiple responses. As such, the following order of response
codes are considered as successful operations:
200, 201, 202, 2XX, 204, default. Furthermore, since multiple content types are not supported,application/jsonwill be used if available. Ifapplication/jsonis not available, then an appropriate content type will be chosen arbitrarily
todos
related:
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
openapi2omg-0.1.0.tar.gz
(5.7 kB
view details)
File details
Details for the file openapi2omg-0.1.0.tar.gz.
File metadata
- Download URL: openapi2omg-0.1.0.tar.gz
- Upload date:
- Size: 5.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.33.0 CPython/3.7.2
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | c002832334abab3ebf41a7789e5d2ee116e715c1a936fc2a8c34448e782895d0 |
|
| MD5 | 372fccdc0c523d940d6af82f328dd3e6 |
|
| BLAKE2b-256 | e3c3465f213f70f82d088fb6772584ce0d84109ab320b78be4a965f7a48729dd |
