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

markdownlint argument -c/--config ignores any input #373

Closed
subwaystation opened this issue Mar 2, 2021 · 4 comments
Closed

markdownlint argument -c/--config ignores any input #373

subwaystation opened this issue Mar 2, 2021 · 4 comments

Comments

@subwaystation
Copy link

Hi @DavidAnson :)

I am trying to use your awesome linter for this nf-core/pangenome#44 pipeline.
Here, we are providing a config file to tell markdownlint how we want the linting done. However, using -c/--config to provide this config file, it is completely ignored.
See the following tiny example:

markdownlint --config markdownlint.yml ./
CHANGELOG.md:8:81 MD013/line-length Line length [Expected: 80; Actual: 93]
CHANGELOG.md:18:81 MD013/line-length Line length [Expected: 80; Actual: 277]

markdownlint.yml:

# Markdownlint configuration file
default: true
line-length: false
no-duplicate-header:
    siblings_only: true
no-inline-html:
    allowed_elements:
        - img
        - p
        - kbd
        - details
        - summary

The line-length errors should not appear!
Changing the name of the config file to .markdownlint.yml, keeping it locally and not setting -c/--config resolves the issue.
But I thought this argument would allow to provide such a config file from anywhere?

I am running your 0.27.0 release on node v15.10.0.

Example files:
Markdown.zip

Thanks for any feedback!

@DavidAnson
Copy link
Owner

From my phone:

@lra
Copy link

lra commented Mar 2, 2021

Could you try --config ./markdownlint.yml?

I did, same issue. Moving the config file to .markdownlint.yaml in the current folder fixes the issue.

@DavidAnson
Copy link
Owner

Please try `v0.27.1', thanks, and sorry for the trouble!

@subwaystation
Copy link
Author

Sorry for reporting in the wrong repository. Thanks for the quick fix @DavidAnson !!!
It works :)

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

No branches or pull requests

3 participants