markdownlint doesn't support "standard" config names

[ruzickap]

Describe the bug
By default markdownlint-cli supports multiple files which contains configuration for this tool:

• .markdownlint.jsonc
• .markdownlint.json
• .markdownlint.yaml
• .markdownlint.yml

Details: https://github.com/igorshubovych/markdownlint-cli/blob/master/README.md?plain=1#L108

It would be nice if megalinter can be compatible with default markdownlint-cli behaviour - work with all of these files by default (and not just with .markdownlint.json).

To Reproduce

Steps to reproduce the behavior:

1. Create markdownlint-cli supported configuration file .markdownlint.yaml.
2. .markdownlint.yaml is not used by default by megalinter

Expected behavior

Megalinter should keep the compatibility with markdownlint-cli and should be able to work with all supported config files by default.

[Kurt-von-Laven]

I would try adding MARKDOWN_MARKDOWNLINT_CONFIG_FILE: LINTER_DEFAULT to your MegaLinter config if you haven't already. I haven't specifically experimented with this setting in the context of Markdownlint, but this approach has served us well for other linters. There may be an argument to be made that LINTER_DEFAULT should be the default behavior in the future (e.g., v7), but it would be a breaking change.

[nvuillam]

In descriptors, config_file_name takes a unique value, whereas for many linters it could be several values, a core enhancement is required

Meanwhile, @Kurt-von-Laven 's solution should do the trick :)

[ruzickap]

Thank you for your help.

Maybe it would be nice if MegaLinter can use the linter's default configuration options / settings in the next major release.

If there is no specific linter/megalinter configuration I suggest to keep this order:

• linter's default configuration
• MegaLinter's default configuration for linter

Thank you...

[nvuillam]

For many linters, MegaLinter is shipped with a default/recommended configuration
Using config_file_name allows to use this default configuration in case there isn't one defined locally, that's why... LINTER_DEFAULT is not by default, and can not be :)

What we can do is allow our internal configuration to have a list of file names, and not a single one, to manage case when the user local linter config file does not have the same name than MegaLinter default config file :)

[ruzickap]

Thank you for explaining it...

Maybe it would make sense to add the following list of markdownlint config files to the internal configuration for markdownlint:

• .markdownlint.jsonc
• .markdownlint.json
• .markdownlint.yaml
• .markdownlint.yml

[nvuillam]

Indeed :)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.