Issue59 #67
Merged
Issue59 #67
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
bufdev
reviewed
Mar 4, 2018
| @@ -153,6 +153,8 @@ func (l *Literal) parse(p *Parser) error { | |||
| type NamedLiteral struct { | |||
| *Literal | |||
| Name string | |||
| // PrintsColon is true when the Name must be printed with a colon suffix | |||
| PrintsColon bool | |||
There was a problem hiding this comment.
Where is this tested?
In previous versions, was the colon printed automatically/was it part of the Name? If so, this is backwards incompatible.
There was a problem hiding this comment.
the colon was never part of the key. this change preserves that information such that any printer/formatter could use it to stay close to the original source.
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.
No description provided.