Drafter 4.0.0-pre.8 #724
Merged
Drafter 4.0.0-pre.8 #724
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enhancements
anyOfin produced JSON Schemas under cases where the properties have been declared in different orders in MSON.#664
Bug Fixes
Fix escaping keys in generated JSON/JSON-Scheme in generated assets
#719
When using a type hint with an array, for example
array[Unknown]. We will now emit a warning when the referenced type does not exist. The invalid type reference will not be present in the parse result.Prevents Drafter from aborting while parsing some API Blueprints due to invalid internal state.