- Fixed issue where params with style deepObject were converted to only one level of key-value pair.
- Add a new argument in input object 'origin' to handle browser specific changes.
- Added handling for type errors encountered on sentry.
- Added support for no-auth as auth in collection when empty object is specified in OAS.
- Bumped up dependencies and dev-dependencies.
- Fixed issue where nested objects present in parameters caused validation mismatches.
- Fixed issue in schema faker where schema with property named deafult was faked incorrectly.
- Fixed wrongly defined maxLength and minLength options for schemaFaker.
- Fix for #337 - Fixed issue where non-required params were not disbled for urlencoded body.
- Fix for #338 - Fixed issue where examples which had non-truthy value were not present in converted collection.
- Fixed issue where resolved schema contain conflicting info regarding pattern and format resulting in validation mismatches.
- Fixed issue where definition for path variable in path caused no matched request for certain paths in validation.
- Fix for #9396 - Fixed validation issue where result contained matched endpoints in incorrect order.
- Fix for #328 - Fixed incorrect usage of id field in sdk.variable and used key.
- Fix for issue where implicit headers generation and validation.
- Fix for #329 - Fixed issue where --test was failing for cli.
- Fixed issue where content type header was reported missing in validation even if present.
- Feature request #9046 - Added support for validation of request body of type urlencoded.
- Fixed issue with import folder flow on respective platform.
- Fixed issue where collection did not contain name for specification with empty string as title.
- Updated description of option to disable optional parameters.
- Fix for #9404 - Fixed issue where incorrect mismatches were reported for valid path variables.
- Fixed issue where validation result contained incorrect path variable indices.
- Fix for #9344 - Fixed issue where for type array examples with more than 2 elements were not used.
- Fix for #9080 - Fixed issue where parameter examples were not used in faked data.
- Fix for #315 - Fixed issue where ConfigFile options are overwritten by CLI options.
- Fix for #69 - Fixed incorrect handling for explodable parameters for resolution schema.
- Added support for disabling optional parameters via option.
- Updated minimum supported node version to v8.
- Fixed issue where schemas in allOf were not resolved correctly.
- Added support for options in CLI converter.
- Bumped up few dev-dependency versions.
- Fixed issue where schema type object with no properties reolved to string.
- Fix for #8474 - Unable to validate primitive data types in req/res body.
- Added support for handling correct media types which were throwing mismatches for validation.
- Added support for internal $ref resolution in validation flows.
- Fixed issue where parameter resolution was "schema" when "example" was specified.
- Add supported formats for schema resolution (deref).
- Fix for #7643, #7914, #9004 - Added support for Auth params in response/example.
- Bumped up multiple dependecies and dev-dependencies versions to keep them up-to-date.
- Updated code coverage tool from deprecated istanbul to nyc.
- Fixed TypeError happening when null parameter value provided.
- Fixed an issue where suggested value for mismatch did not fix corresponding mismatch upon applying.
- Fixed issue where root path was not matched during validation.
- Fixed an issue where transaction was not matching if path had segment with fix and variable parts during valiadtion.
- Fixed issue where URL did not contain baseUrl as host when base url variables are present.
- Fixed issue where collection variable generated for path variables had empty values.
- Fixed issue where invalid deserialisation was happening for param style matrix.
- Added validation tests to improve code coverage.
- Fixed incorrect variable name in schemapack.js.
- Introducing a new option
Optimize conversion
for improving performance of conversion for larger schemas.
- Added support for parameter serialisation in conversion and deserialisation in validation.
- Skipped validation for headers/query-params added by security scheme.
- Fixed incorrect Url and collection variable when path level server is present.
- Fixed issue where empty description property caused mismatch.
- Fixed issue where mismatch was happening even when correct path variable is present.
- Fixed dataPath handling for root property when dataPath is empty string.
- Fixed collection variable ignoring when pattern property is present.
- Added support for collection variables for local servers in suggested request for validation.
- Fixed TypeError happening when empty parameter is provided.
- Fixed invalid transaction json path for headers.
- Added support for collection request as suggested value for missing endpoints.
- Use forked version of oas-resolver to make folder imports work in browser.
- Fixed issues with collection conforimg to JSON schema validation as per v2.1.0 schema.
- Added support for validating content-type header.
- Added support for stricter request matching via option for validation.
- Added missing endpoints from collection info in result of validation.
- Suggest fixes in collection for violated properties in validation.
- Introduced option to validate metadata for validation.
- Use faked value instead of fallback to schema for parameter resolution when set to example.
- Use faked value instead of invalid schema defined example.
- Introduced option to ignore unresolved postman variable mismatches.
- Fixed invalid generated collection for body type formdata.
- Fix for #232 - Changes default auth of requests to null conforming to the JSON schema.
- Fix for #86 - Now global security schemes will be added at the collection level.
- Fix for #3 #57 - Introduced a new option
folderStrategy
, can choose betweenTags
orPath
while creating folders in Postman Collection. - Fixed an issue where undefined was returned as error message while trying to import invalid format.
- Use
minItems
andmaxItems
values if available in schema with type array.
- Change Url to URL in Naming Request option.
- Add missing yaml dependency.
- Added a new function to get meta data from a schema.
- Fix for #169 - Removed unused folderStrategy option.
- Added support for detailed validation body mismatches with option detailedBlobValidation.
- Fix for #8098 - Unable to validate schema with type array.
- Fixed URIError for invalid URI in transaction.
- Fix for #152 - Path references not resolved due to improver handling of special characters.
- Fix for #160 - Added handling for variables in local servers not a part of a URL segment. All path servers to be added as collection variables.
- Unresolved refs will not be stored in schemaResolutionCache.
- Fix for postmanlabs#133 and postmanlabs#101
- Ignore resolving circular references.
- Upgrade commander from 2.3.0 to 2.20.3
- Upgrade postman-collection from 3.5.1 to 3.5.5
- Safely handling invalid reference schemas/properties
- Safely handling malformed URIs and schemas
- Support for multi-file schemas. Added a new input method 'folder'.
- Fix for postmanlabs#162
- Caching faked/resolved schemas for better performance
- Empty input specs don't throw an error anymore
- Fix for postmanlabs#150 - empty examples don't throw exceptions during conversion
- A
(Required)
annotation is added for required parameters
- Not throwing errors for missing schema path entries
- Not throwing errors for invalid schema references
- Not throwing errors for invalid schema.path entries
- Not throwing errors for unknown schema types
- More updated copy for mismatch reasons
- Added missing dependency for async.js
- Updated copy for mismatch reasons
- Returning errors instead of exceptions for invalid schemas
- Fix for duplicate mismatches
- Correct validation against JSON request/response bodies
- Correct JSON paths in response mismatches
- Handling cases where API definition parameters have no schema
- Validating input transaction schema before starting validation
- Forcing path variable descriptions to be strings instead of objects
- Exposing option to hide MISSING_IN_SCHEMA mismatches, hiding them by default
- Consistent response formats, more resilient against invalid schemas
- Deleting 'info.version' from generated collection JSON - it's not required and was causing versioning problems
- Scope-related bugfixes in schema validation flows
- New API to validate requests against a schema
- Fix for postmanlabs#113 - Correct description set for falsy values
- Invalid file paths return a falsy result and a reason (instead of an error)
- Invalid option values don't throw errors anymore
- Readme typo fix (courtesy https://github.com/disposedtrolley)
- Handled cases where the URL query has no description property
- Fix for postmanlabs#117 - Maintaining descriptions for form-urlencoded body params
- Added various options for converting OpenAPI specs into Postman Collections, including controlling how examples are generated
- Request parameters now default to a schema-based value generation, response parameters default to example-based value generation.
- Fix for postmanlabs/swagger2-postman2#21 - Not creating folders at each path level unless required
- Schemas with circular object definitions are imported successfully
- Empty local server definitions not crashing the converter
- Custom JSON headers being picked up for request/response body generation
- Stringifying boolean params if present as query parameters (courtesy https://github.com/Firtzberg)
- Fix for postmanlabs#102 - Not crashing on undefined name/email/description properties
- Fix for postmanlabs#90 - respecting
server
elements defined inside paths - Fix for postmanlabs#98 - respecting
readOnly
andwriteOnly
properies while faking schemas - Fix for postmanlabs#88 - escaping / and ~ characters in
$ref
s (courtesy https://github.com/bzmw)
- Corrected code snippet in README (courtesy https://github.com/simonlampen)
- Fix for postmanlabs#44 - Prevent crashes for specs that contain a root endpoint (courtesy https://github.com/pitpit)
- Ignoring missing body propertes in schema objects
- Added system tests, updated lockfiles for [email protected]
- Fix for postmanlabs/postman-app-support#6538 - parsing JSON correctly from example references
- Fix for postmanlabs/postman-app-support#6538 - handling references in request/response examples
- Fix for postmanlabs/postman-app-support#6500 - manually stringifying number types as a workaround for SDK issues
- Fix for postmanlabs#23 - custom schema formats are not ignored
- Fix for postmanlabs#18 - consistent parsing for URL variables
- Fix for postmanlabs#64 - array params don't cause a crash with schemaFaker disabled (courtesy https://github.com/brpeterman)
- Fix for postmanlabs#52 - allowing $refs to point to paths, not just components
- Fix for postmanlabs#27 - support for allOf-type schemas
- Fix for postmanlabs#45 - trailing slashes in the path don't create empty folders
- Using a placeholder for servers.url in case the spec has a falsy value
- Support for x-postman-meta for including Postman auth in converted collections
- Fix for postmanlabs#36 - Property names with a . in the name are supported during schema faking
- Fix for postmanlabs#47 - Accepting application/vnd.api+json headers as JSON
- Removing unused dependencies
- Fix CLI test commands (courtesy https://github.com/aerotog)
- Fix README typos (courtesy https://github.com/T1l3 and https://github.com/evertharmeling)
- Safe property access to empty content/authHelper objects
- Setting postman_previewLanguage while setting responses
- Not overriding non-string variable types during schema faking
- Not doubly-stringifying string headers
- Removing Node v4/5 from CI
- Ignoring falsy responses in the OAS spec
- Correct error handling/output logging in the executable
- Showing detailed error messages for malformed JSON/YAML
- Fix for postmanlabs#5 - headers with refs to deeply nested components should work
- Fix for postmanlabs#4 - the cwd (not __dirname) is used to look for files specified by -s
- Adding tests for the executable
- Refactoring, restucturing tests
- Adding support for xml chemas
- Enabling travis CI
- Updating README, adding a license, moving to Github
- Converting all console.error to console.warn
- Handling schema.enum when no other schema is specified
- Resolving parameter schemas while creating requests
- Correctly setting path variable descriptions
- Using a browserified json-schema-faker
- Populating the original request in generated example responses
- Infer the response content-type header from the response body
- Generating more human-readable folder/request names from snake_case/camelCase
- Handling nested schemas, correct handling for oneOf/anyOf
- Prefer examples to schemas while generating example response body
- Correct handling for scheme variables in the URL
- Ignoring schema errors for invalid references
- Blocking schema nesting of >20 levels
- Correctly handling empty security sets for requests
- Removing the insecure node-uuid dependency
- Adding default URLs if "server" is absent
- Better indication of lack-of-support for allOf schemas
- Base release