support escaping openapi key words with quotes #512
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.
Me again with an edge-casey one.
Example schemas that use openapi keywords don't get in-lined during bundling, so give this spec:
and the external example ref:
This gets bundled as:
Items is an empty object, so the example is lost.
The usual way of handling reserved words in yaml is quoting them, however this isn't currently handled by the bundling so quoting the
itemskey makes no difference.So, I've added logic to
getNodeKeysto check if the node is quoted, which means after this change the above example gets properly inlined, like:So now if someone has an example which contains a field using an openapi keyword, they can quote it, and it will get properly bundled.