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
I'm working on parsing an OpenAPI spec that I've written in YAML and noticed that this library is having trouble parsing markdown "code" formatting (using inline backticks) that I'm using in one of my descriptions.
This is the error I'm running into:
error: scanner: while scanning for the next token in line 60, column 1
found character that cannot start any token:
`
^
And this is an excerpt of the problematic YAML:
details:
type: stringdescription: >- The details for this pet, if available. In some cases, the value of this property may include newline `\n` characters so that the content can be spread over multiple lines.example: pet details
As you can see, the `\n` at the end of one of the lines seems to be causing the problem and throwing the error in scanner.c. Unfortunately, I'm a bit rusty on my C so I'm not able to provide a fix right now, but I did want to go ahead and log this issue. As far as I can tell, this should be valid YAML. I've attached a sample project to this issue that demonstrates this problem.
I'm working on parsing an OpenAPI spec that I've written in YAML and noticed that this library is having trouble parsing markdown "code" formatting (using inline backticks) that I'm using in one of my descriptions.
This is the error I'm running into:
And this is an excerpt of the problematic YAML:
As you can see, the
`\n`
at the end of one of the lines seems to be causing the problem and throwing the error inscanner.c
. Unfortunately, I'm a bit rusty on my C so I'm not able to provide a fix right now, but I did want to go ahead and log this issue. As far as I can tell, this should be valid YAML. I've attached a sample project to this issue that demonstrates this problem.yams-demo.zip
The text was updated successfully, but these errors were encountered: