[GH-ISSUE #1132] The rule "MD050 - Strong style" should show problems in a file, but does not. #2468

Closed
opened 2026-03-07 20:08:02 +03:00 by kerem · 3 comments
Owner

Originally created by @sergey-rubtsov-05 on GitHub (Feb 19, 2024).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1132

Extension markdownlint for Visual Studio Code does not show "MD050 - Strong style" violations in *.md files.

Environment

  • Visual Studio Code version: 1.86.1 (user setup)
  • markdownlint extension version: 0.54.0

Content of .markdownlint.json

{
    "MD050": {
        "style": "underscore"
    }
}

Content of file which can demonstrate the problem

# Strong text example

**Test.** <-- no problem here, but should be

**Test2** other text. <-- no problem here, but should be

**Test3** - other text. <-- no problem here, but should be

* **Test4** - other text. <-- problems here, as expected

Screenshot

image

Originally created by @sergey-rubtsov-05 on GitHub (Feb 19, 2024). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1132 Extension `markdownlint` for `Visual Studio Code` does not show "MD050 - Strong style" violations in *.md files. # Environment * Visual Studio Code version: `1.86.1` (user setup) * `markdownlint` extension version: `0.54.0` ## Content of `.markdownlint.json` ```json { "MD050": { "style": "underscore" } } ``` # Content of file which can demonstrate the problem ```md # Strong text example **Test.** <-- no problem here, but should be **Test2** other text. <-- no problem here, but should be **Test3** - other text. <-- no problem here, but should be * **Test4** - other text. <-- problems here, as expected ``` ## Screenshot ![image](https://github.com/DavidAnson/vscode-markdownlint/assets/5280736/ce06ffe2-17dd-4a15-a55c-efea2fda3fa3)
kerem 2026-03-07 20:08:02 +03:00
Author
Owner

@DavidAnson commented on GitHub (Feb 19, 2024):

Good one, thanks! This should only happen at the very beginning or very ending of the line. I should have a fix in a few minutes.

<!-- gh-comment-id:1953266139 --> @DavidAnson commented on GitHub (Feb 19, 2024): Good one, thanks! This should only happen at the very beginning or very ending of the line. I should have a fix in a few minutes.
Author
Owner

@sergey-rubtsov-05 commented on GitHub (Feb 20, 2024):

It was really fast. Thank you. When I can expect a release of vs code extension with the fix?

<!-- gh-comment-id:1953656079 --> @sergey-rubtsov-05 commented on GitHub (Feb 20, 2024): It was really fast. Thank you. When I can expect a release of vs code extension with the fix?
Author
Owner

@DavidAnson commented on GitHub (Feb 20, 2024):

I'm not sure when I will start the next round. Probably in a couple of weeks. https://github.com/DavidAnson/markdownlint/blob/main/doc/ReleaseProcess.md

<!-- gh-comment-id:1953667213 --> @DavidAnson commented on GitHub (Feb 20, 2024): I'm not sure when I will start the next round. Probably in a couple of weeks. https://github.com/DavidAnson/markdownlint/blob/main/doc/ReleaseProcess.md
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/markdownlint#2468
No description provided.