[GH-ISSUE #358] MD044 should ignore strings in http links #301

New issue

Closed

opened 2026-03-03 01:25:32 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:25:32 +03:00

Owner

Originally created by @alexbuckgit on GitHub (Dec 16, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/358

MD044 should be configurable to ignore lowercasing in http links, similar to the code_blocks property.

Originally created by @alexbuckgit on GitHub (Dec 16, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/358 MD044 should be configurable to ignore lowercasing in http links, similar to the code_blocks property.

kerem

2026-03-03 01:25:32 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:25:34 +03:00

Author

Owner

@DavidAnson commented on GitHub (Dec 16, 2020):

Note to self: The request is to add a new property that tells this rule to ignore case mismatches in URLs so that a proper name can be forced to be correctly-cased everywhere in the document but not in a case-sensitive URL.

@DavidAnson commented on GitHub (Dec 16, 2020): Note to self: The request is to add a new property that tells this rule to ignore case mismatches in URLs so that a proper name can be forced to be correctly-cased everywhere in the document but not in a case-sensitive URL.

kerem commented

2026-03-03 01:25:34 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 28, 2021):

I think I misunderstood the request. The following Markdown reports only a single violation, ignoring the "wrong" case in the URL. Could you please give an example of something that does not work as you expect?

# Issue 358

The proper case is: JavaScript

So this is wrong: javascript

But it's okay in a URL: https://example.org/javascript.txt

<!-- markdownlint-configure-file {
    "proper-names": {
        "names": [
            "JavaScript"
        ]
    },
    "no-bare-urls": false
} -->

Interactive demo:
https://dlaa.me/markdownlint/#%25m%23%20Issue%20358%0A%0AThe%20proper%20case%20is%3A%20JavaScript%0A%0ASo%20this%20is%20wrong%3A%20javascript%0A%0ABut%20it's%20okay%20in%20a%20URL%3A%20https%3A%2F%2Fexample.org%2Fjavascript.txt%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%20%22JavaScript%22%0A%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%7D%2C%0A%20%20%20%20%22no-bare-urls%22%3A%20false%0A%7D%20--%3E%0A

@DavidAnson commented on GitHub (Jan 28, 2021): I think I misunderstood the request. The following Markdown reports only a single violation, ignoring the "wrong" case in the URL. Could you please give an example of something that does not work as you expect? ```markdown # Issue 358 The proper case is: JavaScript So this is wrong: javascript But it's okay in a URL: https://example.org/javascript.txt  ``` Interactive demo: https://dlaa.me/markdownlint/#%25m%23%20Issue%20358%0A%0AThe%20proper%20case%20is%3A%20JavaScript%0A%0ASo%20this%20is%20wrong%3A%20javascript%0A%0ABut%20it's%20okay%20in%20a%20URL%3A%20https%3A%2F%2Fexample.org%2Fjavascript.txt%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%20%22JavaScript%22%0A%20%20%20%20%20%20%20%20%5D%0A%20%20%20%20%7D%2C%0A%20%20%20%20%22no-bare-urls%22%3A%20false%0A%7D%20--%3E%0A

kerem referenced this issue

2026-03-07 20:04:37 +03:00

[GH-ISSUE #301] Idea of new rule: use slash instead of backslash for image path #2104