mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #409] MD044: Fixes ignore word definitions #340
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#340
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 @skyzyx on GitHub (Jul 1, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/409
0.27.1~0.23.1This issue is related to multiple, similar words that should all remain distinct. I would expect
awsto becomeAWS, but I would not expect@aws-control-towerto becomeAWS.I'm not sure if there's an order of precedence that matters here, but
@aws-control-towergets converted toAWSwhether it's atnames[0],names[1], ornames[2].https://dlaa.me/markdownlint/#%25m%23%20Issue%20409%0A%0AThe%20proper%20case%20is%3A%20%40aws-control-tower%0A%0AJust%20typing%20some%20related%20words%20here%3A%20aws-vault%20and%20AWS%20and%20%40aws-control-tower%20are%20all%20correct.%0A%0A%3C!--%20markdownlint-configure-file%20%7B%0A%20%20%20%20%22proper-names%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22names%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%20%20%20%22AWS%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22aws-vault%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22%40aws-control-tower%22%0A%20%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%7D%0A%7D%20--%3E%0A
@DavidAnson commented on GitHub (Jul 1, 2021):
I expect this to be fixed by the change I already made for #403. With that change, longer names are prioritized first and any substring matches will not be considered. However, I will try your example to verify that. Thanks very much for the excellent demonstration of the problem!
@skyzyx commented on GitHub (Jul 1, 2021):
Thanks. I keep finding small quirks as I'm documenting my code, so hopefully these reports will help make a better product for everybody!
And as an OSS maintainer myself, I want to say thank you for this project and all of the effort you put into it. It's some really great work!