You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,15 @@
1
1
# OpenAPI-Postman Changelog
2
2
3
+
#### v4.5.0 (December 23, 2022)
4
+
* Fixed issue [#11519](https://github.com/postmanlabs/postman-app-support/issues/11519) Collection generated from imported OpenAPI were missing certain properties.
5
+
* Fixed issue [#11227](https://github.com/postmanlabs/postman-app-support/issues/11227) Collection generated produces incorrect XML requests and responses from Open API 3.0 and Swagger 2.0 API definitions.
6
+
* Fixed issue [#11527](https://github.com/postmanlabs/postman-app-support/issues/11527) where generated collection contained empty body when */* was used as content-type.
7
+
* Fixed issue [#626](https://github.com/postmanlabs/openapi-to-postman/issues/626) - Add a new option (includeDeprecated) to handle deprecated properties (operations, parameters, or schema properties).
8
+
* Fixed issue [#643](https://github.com/postmanlabs/openapi-to-postman/issues/643) Generated value for corresponding authorization should be an environment value.
9
+
* Removed travis workflows as GitHub actions are present now.
10
+
* Updated README.md to include Swagger 2.0 and OpenAPI 3.1 support.
11
+
* Updated README.md to include new postman logo.
12
+
3
13
#### v4.4.0 (November 29, 2022)
4
14
* Fixed issue where collection folder name for paths were having extra spaces.
5
15
* Fixed issue where pipelines were failing for certain node version.
Copy file name to clipboardExpand all lines: OPTIONS.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ requestParametersResolution|enum|Example, Schema|Schema|Select whether to genera
8
8
exampleParametersResolution|enum|Example, Schema|Example|Select whether to generate the response parameters based on the [schema](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#schemaObject) or the [example](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#exampleObject) in the schema.|CONVERSION
9
9
folderStrategy|enum|Paths, Tags|Paths|Select whether to create folders according to the spec’s paths or tags.|CONVERSION
10
10
schemaFaker|boolean|-|true|Whether or not schemas should be faked.|CONVERSION
11
-
stackLimit|integer|-|10|Number of nesting limit till which schema resolution will happen. Increasing this limit may result in more time to convert collection depending on complexity of specification. (To make sure this option works correctly "optimizeConversion" option needs to be disabled)|CONVERSION
11
+
stackLimit|integer|-|8|Number of nesting limit till which schema resolution will happen. Increasing this limit may result in more time to convert collection depending on complexity of specification. (To make sure this option works correctly "optimizeConversion" option needs to be disabled)|CONVERSION
12
12
includeAuthInfoInExample|boolean|-|true|Select whether to include authentication parameters in the example request|CONVERSION
13
13
shortValidationErrors|boolean|-|false|Whether detailed error messages are required for request <> schema validation operations.|VALIDATION
14
14
validationPropertiesToIgnore|array|-|[]|Specific properties (parts of a request/response pair) to ignore during validation. Must be sent as an array of strings. Valid inputs in the array: PATHVARIABLE, QUERYPARAM, HEADER, BODY, RESPONSE_HEADER, RESPONSE_BODY|VALIDATION
@@ -23,3 +23,4 @@ disableOptionalParameters|boolean|-|false|Whether to set optional parameters as
23
23
keepImplicitHeaders|boolean|-|false|Whether to keep implicit headers from the OpenAPI specification, which are removed by default.|CONVERSION
24
24
includeWebhooks|boolean|-|false|Select whether to include Webhooks in the generated collection|CONVERSION
25
25
includeReferenceMap|boolean|-|false|Whether or not to include reference map or not as part of output|BUNDLE
26
+
includeDeprecated|boolean|-|true|Select whether to include deprecated operations, parameters, and properties in generated collection or not|CONVERSION, VALIDATION
2.[Using the converter as a NodeJS module](#using-the-converter-as-a-nodejs-module)
17
+
2.[Command Line Interface](#command-line-interface)
18
+
1.[Options](#options)
19
+
2.[Usage](#usage)
20
+
3.[Using the converter as a NodeJS module](#using-the-converter-as-a-nodejs-module)
17
21
1.[Convert Function](#convert)
18
22
2.[Options](#options)
19
23
3.[ConversionResult](#conversionresult)
20
24
4.[Sample usage](#sample-usage)
21
25
5.[Validate function](#validate-function)
22
-
3.[Command Line Interface](#command-line-interface)
23
-
1.[Options](#options)
24
-
2.[Usage](#usage)
25
26
4.[Conversion Schema](#conversion-schema)
26
27
27
28
---
28
29
29
-
## Getting Started
30
+
---
31
+
32
+
### 🚀 We now also support OpenAPI 3.1 and Swagger 2.0 along with OpenAPI 3.0.
33
+
---
34
+
---
35
+
36
+
## 💭 Getting Started
30
37
31
38
To use the converter as a Node module, you need to have a copy of the NodeJS runtime. The easiest way to do this is through npm. If you have NodeJS installed you have npm installed as well.
32
39
@@ -40,7 +47,64 @@ If you want to use the converter in the CLI, install it globally with NPM:
40
47
$ npm i -g openapi-to-postmanv2
41
48
```
42
49
43
-
## Using the converter as a NodeJS module
50
+
51
+
## 📖 Command Line Interface
52
+
53
+
The converter can be used as a CLI tool as well. The following [command line options](#options) are available.
54
+
55
+
`openapi2postmanv2 [options]`
56
+
57
+
### Options
58
+
59
+
-`-s <source>`, `--spec <source>`
60
+
Used to specify the OpenAPI specification (file path) which is to be converted
61
+
62
+
-`-o <destination>`, `--output <destination>`
63
+
Used to specify the destination file in which the collection is to be written
64
+
65
+
-`-p`, `--pretty`
66
+
Used to pretty print the collection object while writing to a file
67
+
68
+
-`-O`, `--options`
69
+
Used to supply options to the converter, for complete options details see [here](/OPTIONS.md)
70
+
71
+
-`-c`, `--options-config`
72
+
Used to supply options to the converter through config file, for complete options details see [here](/OPTIONS.md)
73
+
74
+
-`-t`, `--test`
75
+
Used to test the collection with an in-built sample specification
76
+
77
+
-`-v`, `--version`
78
+
Specifies the version of the converter
79
+
80
+
-`-h`, `--help`
81
+
Specifies all the options along with a few usage examples on the terminal
82
+
83
+
84
+
### Usage
85
+
86
+
- Takes a specification (spec.yaml) as an input and writes to a file (collection.json) with pretty printing and using provided options
- Takes a specification (spec.yaml) as an input and writes to a file (collection.json) with pretty printing and using provided options (Also avoids any `"<Error: Too many levels of nesting to fake this schema>"` kind of errors present in converted collection)
- Takes a specification (spec.yaml) as an input and writes to a file (collection.json) with pretty printing and using provided options (Also avoids any `"<Error: Too many levels of nesting to fake this schema>"` kind of errors present in converted collection)
0 commit comments