starred/markdownlint

Fork 0

mirror of https://github.com/DavidAnson/markdownlint.git synced 2026-04-25 01:05:55 +03:00

[GH-ISSUE #3] MD033 "Inline HTML" should allow exceptions #1

New issue

Closed

opened 2026-03-03 01:22:54 +03:00 by kerem · 8 comments

kerem commented

2026-03-03 01:22:54 +03:00

Owner

Originally created by @rodneyrehm on GitHub (Jul 20, 2015).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/3

My markdown files contain certain html tags (like <kbd>) that just can't be expressed in markdown. I'd suggest to extend the configuration option to accept an array of tags that are considered safe for use in a document.

I generally want to be warned about html in my markdown, but there are situations where I actually need to use the html. I was wondering if there is any way to mark those situations inline, like you would with eslint's /*eslint-disable foobar */. (long shot, I don't see any obvious notation for this…)

Originally created by @rodneyrehm on GitHub (Jul 20, 2015). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/3 My markdown files contain certain html tags (like `<kbd>`) that just can't be expressed in markdown. I'd suggest to extend the configuration option to accept an array of tags that are considered safe for use in a document. I generally want to be warned about html in my markdown, but there are situations where I actually need to use the html. I was wondering if there is any way to mark those situations inline, like you would with eslint's `/*eslint-disable foobar */`. (long shot, I don't see any obvious notation for this…)

kerem added the

enhancement

label

2026-03-03 01:22:54 +03:00

kerem referenced this issue

2026-03-03 01:22:54 +03:00

[GH-ISSUE #1] Consider using key for rules instead of number #3

kerem closed this issue

2026-03-03 01:22:55 +03:00

kerem commented

2026-03-03 01:22:56 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 21, 2015):

FYI, what you talk about in the second paragraph is a little like mivok/markdownlint#16 and might be a nice way to handle this as a special case of a more general pattern.

@DavidAnson commented on GitHub (Jul 21, 2015): FYI, what you talk about in the second paragraph is a little like mivok/markdownlint#16 and might be a nice way to handle this as a special case of a more general pattern.

kerem commented

2026-03-03 01:22:56 +03:00

Author

Owner

@rodneyrehm commented on GitHub (Jul 21, 2015):

yeah, that's pretty much what I was hoping for :)

why are there two projects called markdownlint? Have you guys not tried to merge your code bases?

@rodneyrehm commented on GitHub (Jul 21, 2015): yeah, that's pretty much what I was hoping for :) why are there two projects called markdownlint? Have you guys not tried to merge your code bases?

kerem commented

2026-03-03 01:22:56 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 22, 2015):

The other markdownlint is for Ruby. It didn't seem clean to turn it into a dual Ruby/JavaScript offering, so I created this one for JavaScript after checking with Mark - and then reused as much as I could.

@DavidAnson commented on GitHub (Jul 22, 2015): The other markdownlint is for Ruby. It didn't seem clean to turn it into a dual Ruby/JavaScript offering, so I created this one for JavaScript after checking with Mark - and then reused as much as I could.

kerem commented

2026-03-03 01:22:57 +03:00

Author

Owner

@rodneyrehm commented on GitHub (Jul 22, 2015):

ah, didn't realize it was ruby - good choice, would've done the same :)

@rodneyrehm commented on GitHub (Jul 22, 2015): ah, didn't realize it was ruby - good choice, would've done the same :)

kerem commented

2026-03-03 01:22:57 +03:00

Author

Owner

@DavidAnson commented on GitHub (Dec 6, 2015):

As I revisit this request now, I see that you referenced the ability to disable MD033 inline. That functionality wasn't available at the time, but is now. Is that sufficient for your needs, or are you still interested in more granular control like what your pull request implements? I assume the latter, but wanted to check with you to be sure. Thanks!

@DavidAnson commented on GitHub (Dec 6, 2015): As I revisit this request now, I see that you referenced the ability to disable MD033 inline. That functionality wasn't available at the time, but is now. Is that sufficient for your needs, or are you still interested in more granular control like what your pull request implements? I assume the latter, but wanted to check with you to be sure. Thanks!

kerem commented

2026-03-03 01:22:57 +03:00

Author

Owner

@rodneyrehm commented on GitHub (Dec 6, 2015):

I'm still interested in the tag based filter. It allows me to grant global exceptions for <kbd>, <var> etc. The inline exceptions (via ) would be useful for larger constructs that are, well, the exception.

@rodneyrehm commented on GitHub (Dec 6, 2015): I'm still interested in the tag based filter. It allows me to grant global exceptions for `<kbd>`, `<var>` etc. The inline exceptions (via ``) would be useful for larger constructs that are, well, the exception.

kerem commented

2026-03-03 01:22:57 +03:00

Author

Owner

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

I believe the commit above does what you'd like. If you have any issues with it, please let me know! And thanks for your patience. :)

@DavidAnson commented on GitHub (Dec 16, 2015): I believe the commit above does what you'd like. If you have any issues with it, please let me know! And thanks for your patience. :)

kerem commented

2026-03-03 01:22:57 +03:00

Author

Owner

@rodneyrehm commented on GitHub (Dec 16, 2015):

very nice, thank you!

@rodneyrehm commented on GitHub (Dec 16, 2015): very nice, thank you!

kerem referenced this issue

2026-03-03 02:03:32 +03:00

[PR #1406] [CLOSED] Next #1448

kerem referenced this issue

2026-03-07 20:02:05 +03:00