You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The previous issue (#8145) I opened 2 months ago was fixed by @jfsimon.
Unfortunately the fix only works for a special case but not all.
The current YAML parser in version 2.3.3 works for the following case (as fixed by @jfsimon):
# Comment to be removed
-
# Comment to be removedcontent: | Some header # index.html <body> <h1>My title</h1> </body> Some footer # Comment to be removedtitle: An HTML tutorial
Comments to be stripped are correctly stripped and those to be kept are correctly kept as expected. But if you inverse the associative keys in the yaml string (title first and then content instead of content first and title second) all comments are stripped!
This behavior looks weird but I was able to prove it with a failing unit test as shown below:
Hi,
The previous issue (#8145) I opened 2 months ago was fixed by @jfsimon.
Unfortunately the fix only works for a special case but not all.
The current YAML parser in version 2.3.3 works for the following case (as fixed by @jfsimon):
Comments to be stripped are correctly stripped and those to be kept are correctly kept as expected. But if you inverse the associative keys in the yaml string (
title
first and thencontent
instead ofcontent
first andtitle
second) all comments are stripped!This behavior looks weird but I was able to prove it with a failing unit test as shown below:
The text was updated successfully, but these errors were encountered: