Parse error on YAML headers
See original GitHub issueHi, I want to use this plugin for linting my Docz documentation written in MDX, but the plugin seems unable to parse the YAML headers used for configuration.
Example:
---
name: FollowReveal
route: /follow-reveal
---
# FollowReveal
...
Error:
1:3 error Parsing error: Invalid left-hand side in prefix operation
> 1 | ---
| ^
2 | name: FollowReveal
3 | route: /follow-reveal
4 | ---
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Why do I get the following error: Could not parse YAML header
Your YAML is incorrect, title (maybe because you aligned the : after it with the one from the key above it), is indented...
Read more >mapping values are not allowed in this context "source" ' - R ...
While attempting to knit together an RMarkdown - Bookdown Project - into PDF, I encounter this error: [pandoc warning] Could not parse YAML...
Read more >Not sure where "yaml" error is coming from in RMarkdown
I'm doing an RMarkdown assignment on vectors and matrices for uni class. All my code chunks run fine, except when I try to...
Read more >Fixing “virtual filesystem overlay file all-product-headers.yaml ...
This error could be really annoying, because it blocks the developer to use the lldb resources, such as po to verify values or...
Read more >`po` command fails to work after importing XCFramework
build/all-product-headers.yaml' not found error: virtual filesystem overlay file '/Users/rakshitha/Library/Developer/Xcode/DerivedData/ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@cdfa You need to pass a custom parser, because the ast has been transformed by other parsers/plugins:
However, there still is an error:
I will fix it tonight.
@cdfa Please try v0.3.1
<del> Sorry, it is still buggy for:Wait for a while. </del>