swaggerizer 0.1.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- swaggerizer-0.1.1/LICENSE +201 -0
- swaggerizer-0.1.1/MANIFEST.in +1 -0
- swaggerizer-0.1.1/PKG-INFO +167 -0
- swaggerizer-0.1.1/README.md +145 -0
- swaggerizer-0.1.1/pyproject.toml +37 -0
- swaggerizer-0.1.1/setup.cfg +4 -0
- swaggerizer-0.1.1/swaggerizer/__init__.py +3 -0
- swaggerizer-0.1.1/swaggerizer/cli.py +121 -0
- swaggerizer-0.1.1/swaggerizer/files/customizer.css +70 -0
- swaggerizer-0.1.1/swaggerizer/files/makefile +17 -0
- swaggerizer-0.1.1/swaggerizer/files/openapi.yaml +802 -0
- swaggerizer-0.1.1/swaggerizer/helpers/__init__.py +0 -0
- swaggerizer-0.1.1/swaggerizer/helpers/create_project.py +392 -0
- swaggerizer-0.1.1/swaggerizer/helpers/html_exporter.py +112 -0
- swaggerizer-0.1.1/swaggerizer/helpers/json2yaml_converter.py +44 -0
- swaggerizer-0.1.1/swaggerizer/helpers/json_utils.py +11 -0
- swaggerizer-0.1.1/swaggerizer/helpers/validator.py +67 -0
- swaggerizer-0.1.1/swaggerizer/helpers/yaml2json_converter.py +45 -0
- swaggerizer-0.1.1/swaggerizer.egg-info/PKG-INFO +167 -0
- swaggerizer-0.1.1/swaggerizer.egg-info/SOURCES.txt +23 -0
- swaggerizer-0.1.1/swaggerizer.egg-info/dependency_links.txt +1 -0
- swaggerizer-0.1.1/swaggerizer.egg-info/entry_points.txt +2 -0
- swaggerizer-0.1.1/swaggerizer.egg-info/requires.txt +2 -0
- swaggerizer-0.1.1/swaggerizer.egg-info/top_level.txt +1 -0
- swaggerizer-0.1.1/tests/test_cli.py +21 -0
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
recursive-include swaggerizer/files *
|
|
@@ -0,0 +1,167 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: swaggerizer
|
|
3
|
+
Version: 0.1.1
|
|
4
|
+
Summary: CLI tool to modularize and maintain OpenAPI docs
|
|
5
|
+
Author-email: JR Halterlein <jrhalterlein@gmail.com>
|
|
6
|
+
License: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://www.swaggerizer.com
|
|
8
|
+
Project-URL: Documentation, https://docs.swaggerizer.com
|
|
9
|
+
Project-URL: Source, https://github.com/jrhalterlein/swaggerizer
|
|
10
|
+
Keywords: openapi,swagger,swaggerizer,cli,docs,modularize
|
|
11
|
+
Classifier: Programming Language :: Python :: 3
|
|
12
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
13
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
14
|
+
Classifier: Operating System :: OS Independent
|
|
15
|
+
Classifier: Topic :: Software Development :: Documentation
|
|
16
|
+
Requires-Python: >=3.8
|
|
17
|
+
Description-Content-Type: text/markdown
|
|
18
|
+
License-File: LICENSE
|
|
19
|
+
Requires-Dist: ruamel.yaml<0.19,>=0.18
|
|
20
|
+
Requires-Dist: PyYAML>=6.0
|
|
21
|
+
Dynamic: license-file
|
|
22
|
+
|
|
23
|
+
# Swaggerizer
|
|
24
|
+
|
|
25
|
+
**A lightweight CLI tool to modularize, maintain, and publish OpenAPI docs.**
|
|
26
|
+
|
|
27
|
+
Swaggerizer takes a practical approach to OpenAPI docs management, in the sweet spot between too monolithic or too granular. It breaks up OpenAPI spec files by functional groups and uses a simple make-based system to reassemble them.
|
|
28
|
+
|
|
29
|
+
The Swaggerizer project structure makes it easy for a single writer to build and maintain OpenAPI docs, or for a team of writers to collaborate using a docs-as-code approach.
|
|
30
|
+
|
|
31
|
+
Swaggerizing your OpenAPI docs is _risk free_. It creates a separate source folder with the modularized project files, so you can test it out before committing to anything. Give it a try!
|
|
32
|
+
|
|
33
|
+
## Features
|
|
34
|
+
|
|
35
|
+
- Create a modular OpenAPI project from a single OpenAPI YAML file:
|
|
36
|
+
- Modularize an existing OpenAPI file, or start a new project from the default Petstore file
|
|
37
|
+
- Use make to test and reassemble a single OpenAPI file out of the project/source files
|
|
38
|
+
- Project files are set up in the **openapi_src** sub-directory, with the following structure:
|
|
39
|
+
```
|
|
40
|
+
openapi_src/
|
|
41
|
+
├── 0_intro/ # Basic info, metadata, and tags
|
|
42
|
+
├── 1_endpoints/ # Endpoint descriptions grouped by tag (one file per tag)
|
|
43
|
+
├── 2_components/ # Reusable objects (schemas, parameters, examples, etc.)
|
|
44
|
+
├── 3_misc/ # Additional top-level sections not categorized above
|
|
45
|
+
└── makefile # Custom makefile to generate the final OpenAPI file
|
|
46
|
+
```
|
|
47
|
+
- Other features:
|
|
48
|
+
- Convert OpenAPI files from JSON → YAML or YAML → JSON
|
|
49
|
+
- Validate YAML/JSON file formats
|
|
50
|
+
- Export an OpenAPI YAML file as HTML for publishing
|
|
51
|
+
|
|
52
|
+
## Prerequisites
|
|
53
|
+
|
|
54
|
+
- Python 3.8 or later
|
|
55
|
+
- make
|
|
56
|
+
|
|
57
|
+
## Installation
|
|
58
|
+
|
|
59
|
+
Install using pip:
|
|
60
|
+
|
|
61
|
+
```bash
|
|
62
|
+
pip install swaggerizer
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Verify the installation:
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
swgrzr --help
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
## Quick start
|
|
72
|
+
|
|
73
|
+
Create a new swaggerizer project from your existing **openapi.yaml** file:
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
swgrzr create -i openapi.yaml
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Create a new swaggerizer project from the default Petstore file:
|
|
80
|
+
|
|
81
|
+
```bash
|
|
82
|
+
swgrzr create
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
Build a testing version of the complete OpenAPI file from source:
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
cd openapi_src
|
|
89
|
+
make
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
Copy the current testing version of the OpenAPI file into the parent directory for publishing:
|
|
93
|
+
|
|
94
|
+
```bash
|
|
95
|
+
make final-build
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
Export the OpenAPI YAML file as HTML:
|
|
99
|
+
|
|
100
|
+
```bash
|
|
101
|
+
swgrzr export -i openapi.yaml
|
|
102
|
+
```
|
|
103
|
+
|
|
104
|
+
## CLI usage
|
|
105
|
+
|
|
106
|
+
### Syntax
|
|
107
|
+
|
|
108
|
+
```
|
|
109
|
+
swgrzr OPERATION [options]
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
### Available operations
|
|
113
|
+
|
|
114
|
+
| Operation | Description |
|
|
115
|
+
|-------------|-------------|
|
|
116
|
+
| create | Create a new modularized project from an OpenAPI YAML file. |
|
|
117
|
+
| export | Export the input OpenAPI YAML as a rendered HTML document. |
|
|
118
|
+
| json2yaml | Convert an OpenAPI JSON file to YAML. |
|
|
119
|
+
| yaml2json | Convert an OpenAPI YAML file to JSON. |
|
|
120
|
+
| validate | Validate basic JSON or YAML structure. |
|
|
121
|
+
|
|
122
|
+
### Common options
|
|
123
|
+
|
|
124
|
+
| Option | Description |
|
|
125
|
+
|------------------|-------------|
|
|
126
|
+
| -i, --input | Input file path. Defaults vary by operation. |
|
|
127
|
+
| -o, --output | Output file path. Defaults vary by operation. |
|
|
128
|
+
| -t, --type | Input type for validation (`json`, `yaml`). |
|
|
129
|
+
|
|
130
|
+
## How it works
|
|
131
|
+
|
|
132
|
+
To create a modularized OpenAPI docs project, swaggerizer:
|
|
133
|
+
|
|
134
|
+
1. Loads the source OpenAPI YAML.
|
|
135
|
+
2. Detects the OpenAPI version (`v2` or `v3`).
|
|
136
|
+
3. Extracts and groups the OpenAPI sections.
|
|
137
|
+
4. Generates the modular project source directory.
|
|
138
|
+
5. Adds the makefile to rebuild the spec.
|
|
139
|
+
|
|
140
|
+
## Source code overview
|
|
141
|
+
|
|
142
|
+
```
|
|
143
|
+
swaggerizer/ # Metadata and packaging
|
|
144
|
+
├── swaggerizer/ # Python app source
|
|
145
|
+
│ ├── cli.py # CLI entry point
|
|
146
|
+
│ ├── files/ # Default assets
|
|
147
|
+
│ └── helpers/ # Helper modules
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
## How to help
|
|
151
|
+
|
|
152
|
+
Feedback is appreciated!
|
|
153
|
+
|
|
154
|
+
Please:
|
|
155
|
+
|
|
156
|
+
- Report bugs or unexpected behavior.
|
|
157
|
+
- Propose enhancements to CLI commands or options.
|
|
158
|
+
|
|
159
|
+
To contribute:
|
|
160
|
+
|
|
161
|
+
1. Fork the swaggerizer repo.
|
|
162
|
+
2. Create a branch for your changes.
|
|
163
|
+
3. Run tests before submitting.
|
|
164
|
+
4. Open a pull request describing your changes and motivation.
|
|
165
|
+
|
|
166
|
+
Smaller, focused pull requests are preferred.
|
|
167
|
+
|
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# Swaggerizer
|
|
2
|
+
|
|
3
|
+
**A lightweight CLI tool to modularize, maintain, and publish OpenAPI docs.**
|
|
4
|
+
|
|
5
|
+
Swaggerizer takes a practical approach to OpenAPI docs management, in the sweet spot between too monolithic or too granular. It breaks up OpenAPI spec files by functional groups and uses a simple make-based system to reassemble them.
|
|
6
|
+
|
|
7
|
+
The Swaggerizer project structure makes it easy for a single writer to build and maintain OpenAPI docs, or for a team of writers to collaborate using a docs-as-code approach.
|
|
8
|
+
|
|
9
|
+
Swaggerizing your OpenAPI docs is _risk free_. It creates a separate source folder with the modularized project files, so you can test it out before committing to anything. Give it a try!
|
|
10
|
+
|
|
11
|
+
## Features
|
|
12
|
+
|
|
13
|
+
- Create a modular OpenAPI project from a single OpenAPI YAML file:
|
|
14
|
+
- Modularize an existing OpenAPI file, or start a new project from the default Petstore file
|
|
15
|
+
- Use make to test and reassemble a single OpenAPI file out of the project/source files
|
|
16
|
+
- Project files are set up in the **openapi_src** sub-directory, with the following structure:
|
|
17
|
+
```
|
|
18
|
+
openapi_src/
|
|
19
|
+
├── 0_intro/ # Basic info, metadata, and tags
|
|
20
|
+
├── 1_endpoints/ # Endpoint descriptions grouped by tag (one file per tag)
|
|
21
|
+
├── 2_components/ # Reusable objects (schemas, parameters, examples, etc.)
|
|
22
|
+
├── 3_misc/ # Additional top-level sections not categorized above
|
|
23
|
+
└── makefile # Custom makefile to generate the final OpenAPI file
|
|
24
|
+
```
|
|
25
|
+
- Other features:
|
|
26
|
+
- Convert OpenAPI files from JSON → YAML or YAML → JSON
|
|
27
|
+
- Validate YAML/JSON file formats
|
|
28
|
+
- Export an OpenAPI YAML file as HTML for publishing
|
|
29
|
+
|
|
30
|
+
## Prerequisites
|
|
31
|
+
|
|
32
|
+
- Python 3.8 or later
|
|
33
|
+
- make
|
|
34
|
+
|
|
35
|
+
## Installation
|
|
36
|
+
|
|
37
|
+
Install using pip:
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
pip install swaggerizer
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
Verify the installation:
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
swgrzr --help
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Quick start
|
|
50
|
+
|
|
51
|
+
Create a new swaggerizer project from your existing **openapi.yaml** file:
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
swgrzr create -i openapi.yaml
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
Create a new swaggerizer project from the default Petstore file:
|
|
58
|
+
|
|
59
|
+
```bash
|
|
60
|
+
swgrzr create
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
Build a testing version of the complete OpenAPI file from source:
|
|
64
|
+
|
|
65
|
+
```bash
|
|
66
|
+
cd openapi_src
|
|
67
|
+
make
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
Copy the current testing version of the OpenAPI file into the parent directory for publishing:
|
|
71
|
+
|
|
72
|
+
```bash
|
|
73
|
+
make final-build
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
Export the OpenAPI YAML file as HTML:
|
|
77
|
+
|
|
78
|
+
```bash
|
|
79
|
+
swgrzr export -i openapi.yaml
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
## CLI usage
|
|
83
|
+
|
|
84
|
+
### Syntax
|
|
85
|
+
|
|
86
|
+
```
|
|
87
|
+
swgrzr OPERATION [options]
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### Available operations
|
|
91
|
+
|
|
92
|
+
| Operation | Description |
|
|
93
|
+
|-------------|-------------|
|
|
94
|
+
| create | Create a new modularized project from an OpenAPI YAML file. |
|
|
95
|
+
| export | Export the input OpenAPI YAML as a rendered HTML document. |
|
|
96
|
+
| json2yaml | Convert an OpenAPI JSON file to YAML. |
|
|
97
|
+
| yaml2json | Convert an OpenAPI YAML file to JSON. |
|
|
98
|
+
| validate | Validate basic JSON or YAML structure. |
|
|
99
|
+
|
|
100
|
+
### Common options
|
|
101
|
+
|
|
102
|
+
| Option | Description |
|
|
103
|
+
|------------------|-------------|
|
|
104
|
+
| -i, --input | Input file path. Defaults vary by operation. |
|
|
105
|
+
| -o, --output | Output file path. Defaults vary by operation. |
|
|
106
|
+
| -t, --type | Input type for validation (`json`, `yaml`). |
|
|
107
|
+
|
|
108
|
+
## How it works
|
|
109
|
+
|
|
110
|
+
To create a modularized OpenAPI docs project, swaggerizer:
|
|
111
|
+
|
|
112
|
+
1. Loads the source OpenAPI YAML.
|
|
113
|
+
2. Detects the OpenAPI version (`v2` or `v3`).
|
|
114
|
+
3. Extracts and groups the OpenAPI sections.
|
|
115
|
+
4. Generates the modular project source directory.
|
|
116
|
+
5. Adds the makefile to rebuild the spec.
|
|
117
|
+
|
|
118
|
+
## Source code overview
|
|
119
|
+
|
|
120
|
+
```
|
|
121
|
+
swaggerizer/ # Metadata and packaging
|
|
122
|
+
├── swaggerizer/ # Python app source
|
|
123
|
+
│ ├── cli.py # CLI entry point
|
|
124
|
+
│ ├── files/ # Default assets
|
|
125
|
+
│ └── helpers/ # Helper modules
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
## How to help
|
|
129
|
+
|
|
130
|
+
Feedback is appreciated!
|
|
131
|
+
|
|
132
|
+
Please:
|
|
133
|
+
|
|
134
|
+
- Report bugs or unexpected behavior.
|
|
135
|
+
- Propose enhancements to CLI commands or options.
|
|
136
|
+
|
|
137
|
+
To contribute:
|
|
138
|
+
|
|
139
|
+
1. Fork the swaggerizer repo.
|
|
140
|
+
2. Create a branch for your changes.
|
|
141
|
+
3. Run tests before submitting.
|
|
142
|
+
4. Open a pull request describing your changes and motivation.
|
|
143
|
+
|
|
144
|
+
Smaller, focused pull requests are preferred.
|
|
145
|
+
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
[build-system]
|
|
2
|
+
requires = ["setuptools>=69", "wheel"]
|
|
3
|
+
build-backend = "setuptools.build_meta"
|
|
4
|
+
|
|
5
|
+
[project]
|
|
6
|
+
name = "swaggerizer"
|
|
7
|
+
version = "0.1.1"
|
|
8
|
+
description = "CLI tool to modularize and maintain OpenAPI docs"
|
|
9
|
+
readme = "README.md"
|
|
10
|
+
requires-python = ">=3.8"
|
|
11
|
+
license = { text = "Apache-2.0" }
|
|
12
|
+
authors = [{ name = "JR Halterlein", email = "jrhalterlein@gmail.com" }]
|
|
13
|
+
dependencies = ["ruamel.yaml>=0.18,<0.19", "PyYAML>=6.0"]
|
|
14
|
+
keywords = ["openapi", "swagger", "swaggerizer", "cli", "docs", "modularize"]
|
|
15
|
+
classifiers = [
|
|
16
|
+
"Programming Language :: Python :: 3",
|
|
17
|
+
"Programming Language :: Python :: 3 :: Only",
|
|
18
|
+
"License :: OSI Approved :: Apache Software License",
|
|
19
|
+
"Operating System :: OS Independent",
|
|
20
|
+
"Topic :: Software Development :: Documentation"
|
|
21
|
+
]
|
|
22
|
+
|
|
23
|
+
[project.scripts]
|
|
24
|
+
swgrzr = "swaggerizer.cli:main"
|
|
25
|
+
|
|
26
|
+
[project.urls]
|
|
27
|
+
Homepage = "https://www.swaggerizer.com"
|
|
28
|
+
Documentation = "https://docs.swaggerizer.com"
|
|
29
|
+
Source = "https://github.com/jrhalterlein/swaggerizer"
|
|
30
|
+
|
|
31
|
+
[tool.setuptools.packages.find]
|
|
32
|
+
where = ["."]
|
|
33
|
+
include = ["swaggerizer*"]
|
|
34
|
+
|
|
35
|
+
[tool.setuptools.package-data]
|
|
36
|
+
"swaggerizer" = ["files/*", "files/**"]
|
|
37
|
+
|
|
@@ -0,0 +1,121 @@
|
|
|
1
|
+
import argparse, os, shutil
|
|
2
|
+
from .helpers.create_project import Swaggerizer
|
|
3
|
+
from .helpers.html_exporter import HTMLExporter
|
|
4
|
+
from .helpers.json2yaml_converter import json2YamlConverter
|
|
5
|
+
from .helpers.yaml2json_converter import yaml2JsonConverter
|
|
6
|
+
from .helpers.validator import validator
|
|
7
|
+
|
|
8
|
+
|
|
9
|
+
def checkCreateOutputDir(output_arg):
|
|
10
|
+
# Create output directory if needed
|
|
11
|
+
output_dir = os.path.dirname(output_arg)
|
|
12
|
+
if output_dir and not os.path.exists(output_dir):
|
|
13
|
+
os.makedirs(output_dir)
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
def main():
|
|
17
|
+
parser = argparse.ArgumentParser(
|
|
18
|
+
description="Swaggerize your API documentation.",
|
|
19
|
+
formatter_class=argparse.RawTextHelpFormatter
|
|
20
|
+
)
|
|
21
|
+
parser.add_argument(
|
|
22
|
+
"operation",
|
|
23
|
+
metavar="OPERATION",
|
|
24
|
+
choices=["create", "export", "json2yaml", "yaml2json", "validate"],
|
|
25
|
+
help=("Available operations:\n"
|
|
26
|
+
" create = Create new modularized OpenAPI docs project\n"
|
|
27
|
+
" export = Export OpenAPI YAML file as HTML\n"
|
|
28
|
+
" json2yaml = Convert OpenAPI JSON file to YAML\n"
|
|
29
|
+
" yaml2json = Convert OpenAPI YAML file to JSON\n"
|
|
30
|
+
" validate = Validate basic JSON or YAML format"
|
|
31
|
+
)
|
|
32
|
+
)
|
|
33
|
+
parser.add_argument(
|
|
34
|
+
"-i", "--input",
|
|
35
|
+
metavar="IN_FILE",
|
|
36
|
+
default=None,
|
|
37
|
+
help=("Input file or path. Default value per operation:\n"
|
|
38
|
+
" create = './openapi.yaml'\n"
|
|
39
|
+
" export = './openapi.yaml'\n"
|
|
40
|
+
" json2yaml = './openapi.json'\n"
|
|
41
|
+
" yaml2json = './openapi.yaml'"
|
|
42
|
+
)
|
|
43
|
+
)
|
|
44
|
+
parser.add_argument(
|
|
45
|
+
"-o", "--output",
|
|
46
|
+
metavar="OUT_FILE",
|
|
47
|
+
default=None,
|
|
48
|
+
help=("Output file or path. Default value per operation:\n"
|
|
49
|
+
" export = '{IN_FILE}.html'\n"
|
|
50
|
+
" json2yaml = '{IN_FILE}.yaml'\n"
|
|
51
|
+
" yaml2json = '{IN_FILE}.json'"
|
|
52
|
+
)
|
|
53
|
+
|
|
54
|
+
)
|
|
55
|
+
parser.add_argument(
|
|
56
|
+
"-t", "--type",
|
|
57
|
+
metavar="FILE_TYPE",
|
|
58
|
+
default=None,
|
|
59
|
+
choices=["json", "yaml"],
|
|
60
|
+
help=("File type for validate operation. Omit to get type\n"
|
|
61
|
+
"from file extension. Possible values:\n"
|
|
62
|
+
" json = Validate basic JSON format.\n"
|
|
63
|
+
" yaml = Validate basic YAML format."
|
|
64
|
+
)
|
|
65
|
+
)
|
|
66
|
+
|
|
67
|
+
# Parse arguments
|
|
68
|
+
args = parser.parse_args()
|
|
69
|
+
|
|
70
|
+
# Handle the requested operation
|
|
71
|
+
if args.operation == "create":
|
|
72
|
+
# Define default input
|
|
73
|
+
args.input = args.input or "openapi.yaml"
|
|
74
|
+
|
|
75
|
+
# Swaggerize it
|
|
76
|
+
project = Swaggerizer(args.input)
|
|
77
|
+
project.create()
|
|
78
|
+
|
|
79
|
+
elif args.operation == "export":
|
|
80
|
+
# Define default input
|
|
81
|
+
args.input = args.input or "openapi.yaml"
|
|
82
|
+
|
|
83
|
+
# Make sure output dir exists if specified
|
|
84
|
+
if args.output:
|
|
85
|
+
checkCreateOutputDir(args.output)
|
|
86
|
+
|
|
87
|
+
# Export the HTML
|
|
88
|
+
exporter = HTMLExporter(args.input, args.output)
|
|
89
|
+
exporter.export()
|
|
90
|
+
|
|
91
|
+
elif args.operation == "json2yaml":
|
|
92
|
+
# Define default input
|
|
93
|
+
args.input = args.input or "openapi.json"
|
|
94
|
+
|
|
95
|
+
# Make sure output dir exists if specified
|
|
96
|
+
if args.output:
|
|
97
|
+
checkCreateOutputDir(args.output)
|
|
98
|
+
|
|
99
|
+
# Convert the JSON to YAML
|
|
100
|
+
converter = json2YamlConverter(args.input, args.output)
|
|
101
|
+
converter.convert()
|
|
102
|
+
|
|
103
|
+
elif args.operation == "yaml2json":
|
|
104
|
+
# Define default input
|
|
105
|
+
args.input = args.input or "openapi.yaml"
|
|
106
|
+
|
|
107
|
+
# Make sure output dir exists if specified
|
|
108
|
+
if args.output:
|
|
109
|
+
checkCreateOutputDir(args.output)
|
|
110
|
+
|
|
111
|
+
# Convert the YAML to JSON
|
|
112
|
+
converter = yaml2JsonConverter(args.input, args.output)
|
|
113
|
+
converter.convert()
|
|
114
|
+
|
|
115
|
+
elif args.operation == "validate":
|
|
116
|
+
# Define default input
|
|
117
|
+
args.input = args.input or "openapi.yaml"
|
|
118
|
+
|
|
119
|
+
# Validate the file
|
|
120
|
+
validator.validate(args.input, args.type)
|
|
121
|
+
|