Add option to output JS Maps, add generic support for iterables #51
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.
Fixes #46, fixes #49, fixes #50
On the YAML -> JS side, this adds a new option
mapAsMap
, with which YAML mappings are represented in JS asMap
rather thanObject
instances:The specific benefit of this is the ability to natively use non-string keys in mappings.
Then on the JS -> YAML side, iterable values are now supported by
createNode()
. The default is to parse them as sequences, butMap
and its descendants are parsed as mappings.