Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Yaml] fix lexing nested sequences/mappings#33763
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
fabpot commentedAug 11, 2020
@xabbuh Is it something you're still willing to work on? |
4279223 to800a703Compare
simonberger left a comment
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.
Nicely done.
I just missed a test with strings in mappings/sequences containing brackets which has been fixed in this PR as well.
As a possible test the following part ofinlineNotationSpanningMultipleLinesProvider passed successfully.
'nested collections containing strings with bracket chars' => [ [['ba[r'], ['[ba]r'], ['bar]'], ['foo' => 'bar{'], ['foo' => 'b{ar}'], ['foo' => 'bar}']], <<<YAML[ [ "ba[r" ], [ '[ba]r' ], [ "bar]" ], { foo: "bar{" }, { foo: "b{ar}" }, { foo: 'bar}' }]Uh oh!
There was an error while loading.Please reload this page.
xabbuh commentedNov 15, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
728cba9 tof21bd46Comparexabbuh commentedNov 15, 2020
This is ready to be reviewed. |
Uh oh!
There was an error while loading.Please reload this page.
simonberger left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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.
Escaped quotes are not yet skipped inlexInlineQuotedString and are leading to problems for example in this yaml test:
[ ["te\"st"],["test"]]Another simple error case is:
[ ["te\"st]"]]d418d1d to0e38c33Comparesimonberger commentedNov 17, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There is (now) another small issue with escaped backslashes in quotes treated as the escape for the quote. I got a segmentation error writing the yam like this: |
xabbuh commentedNov 17, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Did you mean |
simonberger commentedNov 17, 2020
Depends how it is declared. In HEREDOC
|
xabbuh commentedNov 17, 2020
@simonberger I don't see a difference here (see alsohttps://3v4l.org/iOVjl). Could you please send a PR with a test case that you have in mind to my branch if you still think that something isn't working as expected? |
simonberger commentedNov 17, 2020
@xabbuh I am sorry. This was indeed my wrong test. |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
simonberger left a comment
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.
My pleasure. LGTM now.
fabpot commentedNov 19, 2020
Thank you@xabbuh. |
derrabus commentedNov 21, 2020
@xabbuh Can I ask you to merge 4.4 into 5.1? This PR gives me a headache. |
xabbuh commentedNov 21, 2020
@derrabus done 👍 |
Uh oh!
There was an error while loading.Please reload this page.