-
-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixed broken serialization of duplicated entries in sequences #205
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
'use strict'; | ||
|
||
|
||
var assert = require('assert'); | ||
var yaml = require('../../'); | ||
|
||
|
||
test('Duplicated objects within array', function () { | ||
var obj = { test: 'canary' }; | ||
var arrayWithRefs = [ obj, obj ]; | ||
|
||
var obtained = yaml.load(yaml.dump(arrayWithRefs)); | ||
|
||
assert.equal(obtained[0].test, 'canary'); | ||
assert.equal(obtained[0], obtained[1]); | ||
}); | ||
|
||
test('Duplicated arrays within array', function () { | ||
var array = [ 0, 1 ]; | ||
var arrayWithRefs = [ array, array ]; | ||
|
||
var obtained = yaml.load(yaml.dump(arrayWithRefs)); | ||
|
||
assert.equal(obtained[0][0], 0); | ||
assert.equal(obtained[0][1], 1); | ||
assert.equal(obtained[0], obtained[1]); | ||
}); |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this removed completely? Why? AFAIK this was intended for cases like the following:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But probably I'm mistaken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I remembered. It's for anchors on top-level nodes. So the question stands: Why is this removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I removed it completely. I will check if your example still works correctly. In the meantime my reasoning to remove this condition:
The problem with the incorrectly prepended YAML alias names only occurred if
compact
was true.writeNode
is called withcompact = true
from line 536, line 625 and line 830.(0 === level ? '\n' : '')
is responsible for prepending the alias for top level objects, i.e. for calls from line 830. For example, this condition ensures that we getinstead of
&ref_0- *ref_0
The two other positions which called
writeNode
withcompact = true
were not handled correctly by this condition.Since I set
compact
tofalse
when an alias is prepended, I think that this condition is not necessary anymore. Without the removal of(0 === level ? '\n' : '')
we would now actually get(note the extra empty line)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just tested your example.
is still correctly serialized as
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, OK. Thanks for explanation.