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

Add support to YAML syntax for the .markdownlintrc config file #319

Open
rogerluan opened this issue Aug 29, 2022 · 4 comments
Open

Add support to YAML syntax for the .markdownlintrc config file #319

rogerluan opened this issue Aug 29, 2022 · 4 comments

Comments

@rogerluan
Copy link
Contributor

Request originated from this discussion: #317 (comment)

We have to update the documentation that was updated here #318 when this feature gets implemented

Super valuable, as yaml is more user friendly than JSON, and technically allows comments to be written :)

@edbrannin
Copy link

and technically allows comments to be written

It seems like a JSON ~/.markdownlintrc with comments could actually work...

Comments are stripped from JSON config via strip-json-comments.

...but it doesn't work in practice. Maybe if the current version of rc were used?

I can't actually tell which version is being used currently, since it's not listed in package.json and there isn't a package-lock.json committed.

@DavidAnson
Copy link
Collaborator

It's run-con which replaced rc:

"run-con": "~1.3.2"

And here's a link to package-lock: https://github.com/igorshubovych/markdownlint-cli/blob/master/package-lock.json

@rogerluan
Copy link
Contributor Author

Any down side of supporting yaml? From a technical PoV it's quite simple to add support to it AFAIK 😮

@DavidAnson
Copy link
Collaborator

.markdownlintrc is a weird "it can be anything" file that is not supported by CLI2 or the VS Code extension. (Both support YAML via .markdownlint.yaml and similar.) I'd prefer not to invest further in this file format.

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

3 participants