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

Support .markdownlint-cli2.yml #509

Open
fernandoaleman opened this issue Feb 22, 2025 · 4 comments
Open

Support .markdownlint-cli2.yml #509

fernandoaleman opened this issue Feb 22, 2025 · 4 comments
Labels
question Further information is requested

Comments

@fernandoaleman
Copy link

Hello David,

This is just a nit picky thing, but is there any reason why we can't use a .markdownlint-cli2.yml with a yml extension, vs only the yaml extension? I use a .yml extension for all my yaml files and my OCD simply hates to have one lonely .yaml file. 😄

@DavidAnson
Copy link
Owner

There is a relevant discussion here: #304 (comment)

@DavidAnson DavidAnson added the question Further information is requested label Feb 22, 2025
@fernandoaleman
Copy link
Author

Thanks @DavidAnson for providing the comment reference above. I read through it and can understand why simply using .js or .json may possibly be "ambiguous", but how would using .yml be ambiguous as opposed to .yaml? Just trying to understand the logic since .yml is a very commonly used extension.

@DavidAnson
Copy link
Owner

I already do not support JSON and YML extensions for the new options file format (preferring JSONC and YAML) for simplicity ...

@DavidAnson
Copy link
Owner

Here's a duplicate issue with a bit more context: #392

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants