Adding an option to dump symbols in a more natural format#2
Open
camertron wants to merge 1 commit into
Open
Conversation
|
I am strongly in favor of this pull request :-) |
This file contains hidden or 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
2 participants
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.
The current ya2yaml dump of a Ruby symbol looks like this:
:batman.ya2yamlWhile this works, it's a little hard on the eyes. Symbols as hash keys are even worse:
{ :batman => "dark knight" }.ya2yamlThe Ruby YAML parser knows how to deal with symbols natively using the colon syntax, so why not output them that way? This pull request adds an option to
#ya2yamlcalled:use_natural_symbolsthat emits symbols prefixed by the more familiar colon::batman.ya2yaml(:use_natural_symbols => true){ :batman => "dark knight" }.ya2yaml(:use_natural_symbols => true)