Open pjlsergeant opened 12 years ago
Hello, I was having the same problem but if you read the Readme you will see that this has pretty sparse support for the YAML spec. I did find this though while I was Googling for alternatives https://code.google.com/p/javascript-yaml-parser/ and I started a branch here https://github.com/RumpleFraggle/javascript-yaml-parser
I want to stress as much as possible that I can take absolutely no credit for this. I just re-posted the SVN as a GIT
Thanks for emailing me this!
On Tuesday, January 10, 2012, Rumple Fraggle < reply@reply.github.com> wrote:
Hello, I was having the same problem but if you read the Readme you will see that this has pretty sparse support for the YAML spec. I did find this though while I was Googling for alternatives https://code.google.com/p/javascript-yaml-parser/ and I started a branch here https://github.com/RumpleFraggle/javascript-yaml-parser
I want to stress as much as possible that I can take absolutely no credit for this. I just re-posted the SVN as a GIT
Reply to this email directly or view it on GitHub: https://github.com/visionmedia/js-yaml/issues/36#issuecomment-3426281
I think that is your issue: https://github.com/visionmedia/js-yaml/issues/45
Given
I'm getting:
Which is a shame. The YAML looks valid to me (and is happily parsed by the Perl YAML modules I'm using)