mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 17:26:22 +03:00
[GH-ISSUE #373] markdownlint argument -c/--config ignores any input #313
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#313
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @subwaystation on GitHub (Mar 2, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/373
Hi @DavidAnson :)
I am trying to use your awesome linter for this https://github.com/nf-core/pangenome/pull/44 pipeline.
Here, we are providing a config file to tell markdownlint how we want the linting done. However, using
-c/--configto provide this config file, it is completely ignored.See the following tiny example:
markdownlint.yml:The line-length errors should not appear!
Changing the name of the config file to
.markdownlint.yml, keeping it locally and not setting-c/--configresolves 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 commented on GitHub (Mar 2, 2021):
From my phone:
--config ./markdownlint.yml?@lra commented on GitHub (Mar 2, 2021):
I did, same issue. Moving the config file to
.markdownlint.yamlin the current folder fixes the issue.@DavidAnson commented on GitHub (Mar 2, 2021):
Please try `v0.27.1', thanks, and sorry for the trouble!
@subwaystation commented on GitHub (Mar 2, 2021):
Sorry for reporting in the wrong repository. Thanks for the quick fix @DavidAnson !!!
It works :)