mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 17:26:22 +03:00
[GH-ISSUE #343] Configuration : Unable to disable rules by their ID #2142
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#2142
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 @mat-m on GitHub (Oct 17, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/343
Hello,
With vscode-markdownlint 0.37.1, and markdownlint-cli2 0.0.10, I cannot disable a rule by its ID, but only by its alias.
This is NOT OK:
although this does:
Is it a bug or a feature, like IDs are reserved for rules configuration ?
@DavidAnson commented on GitHub (Oct 18, 2020):
This is not expected and there are various tests that exist to make sure this works. Could you please give more information about your scenario? Is there another configuration file that is enabling that rule by name? If so, then it may not work to later disable it by number. but the simple scenario of disabling by number should definitely work.
@mat-m commented on GitHub (Oct 18, 2020):
Hello,
You can try with my use case:
https://github.com/thoughtbot/rcm.git.markdownlint.jsonwith contents aboveCONTRIBUTING.md(Contributing and Governance are both level 1)Let me know your results
@DavidAnson commented on GitHub (Oct 18, 2020):
I see the expected behavior which is that disabling the rule by either
MD025orsingle-titlesuccessfully disables the rule.[Code shows the same 8 errors above; MD025 is not reported. Extension version
0.37.1]Please have another look at your configuration. I'd guess maybe a typo crept in somewhere and it wasn't really
MD025?@mat-m commented on GitHub (Oct 21, 2020):
Can't reproduce today neither.
Should have been a non-visible char or something, since pasting in this thread gave the right values.
As in the song, "It's only mystery, and I like it"