Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

if .markdownlint.yaml is empty, markdown lint crashes with Error: Unable to parse '.markdownlint.yaml'; Parser 0: Unable to parse JSONC content, ValueExpected (offset 0, length 0) #1523

Open
onerandomusername opened this issue Feb 27, 2025 · 1 comment

Comments

@onerandomusername
Copy link

No description provided.

@DavidAnson DavidAnson transferred this issue from DavidAnson/vscode-markdownlint Feb 28, 2025
@DavidAnson
Copy link
Owner

This is really interesting, thanks! When https://github.com/nodeca/js-yaml successfully parses an empty file (or one with only comments), it returns null. It's documented to do that and I see now that YAML documents could return a string or a number instead of an object - which I had not expected. I'll fix this soon, though it'll be a little bit before the fix makes it to a VS Code extension release.

@DavidAnson DavidAnson added the bug label Feb 28, 2025
DavidAnson added a commit that referenced this issue Mar 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants