[GH-ISSUE #1917] MD060: Aligned update breaking existing tables #778

Open
opened 2026-03-03 01:29:48 +03:00 by kerem · 1 comment
Owner

Originally created by @texonidas on GitHub (Jan 19, 2026).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1917

In all of our existing tables, we have used the following syntax:

| Name | Version |
|------|---------|
| A Name | v1.0.0 |

Noting the difference in spacing between row separator lines (no space), and value lines (single space). After we have returned from the holiday break this is now no longer valid according to markdown lint. Is there a simple way for us to continue using the existing behaviour that allows this as a valid table?

Originally created by @texonidas on GitHub (Jan 19, 2026). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1917 <!-- Thank you for taking the time to report an issue! When deciding where to open an issue, please note there are multiple projects under the markdownlint umbrella: - https://github.com/DavidAnson/markdownlint : This is the core JavaScript/Node.js library and is used by other tools. Most issues with implementation and rule behavior belong here. - https://github.com/igorshubovych/markdownlint-cli : This is the original CLI for markdownlint. Issues specific to CLI belong here. - https://github.com/DavidAnson/markdownlint-cli2 : This is a newer CLI for markdownlint and is used by other tools. Issues specific to CLI2 belong here. - https://github.com/DavidAnson/vscode-markdownlint : This is the Visual Studio Code extension for markdownlint. Issues specific to VS Code belong here. - https://github.com/DavidAnson/markdownlint-cli2-action : This is a GitHub Action for markdownlint. Issues specific to the Action belong here. - https://github.com/markdownlint/markdownlint : This is the original markdownlint implementation for Ruby. All Ruby-related issues belong here. Before creating an issue, it's a good practice to search existing issues for something similar. If your issue has already been reported, please update the existing one with any new information. It's also good to review the documentation for any relevant details. When describing an issue, the following information is helpful: - What did you do? - What did you expect to happen? - What actually happened? - What messages or errors were there? - How can the issue be reproduced? - What version were you using? - What operating system were you using? The simplest demonstration of a problem is the most helpful. Small examples can be pasted into the issue description. (Be sure to paste as code so GitHub doesn't render the example in Markdown.) For larger examples, linking to a repository or file is more appropriate. Before proposing a new rule, please review the existing suggestions: https://github.com/DavidAnson/markdownlint/issues?q=is%3Aissue+is%3Aopen+label%3A%22new+rule%22 Thank you! --> In all of our existing tables, we have used the following syntax: ``` | Name | Version | |------|---------| | A Name | v1.0.0 | ``` Noting the difference in spacing between row separator lines (no space), and value lines (single space). After we have returned from the holiday break this is now no longer valid according to markdown lint. Is there a simple way for us to continue using the existing behaviour that allows this as a valid table?
Author
Owner

@DavidAnson commented on GitHub (Jan 19, 2026):

You could disable the rule or modify the table to match one of the three supported styles. Your example seems closest to the "compact" style and would only require edits to the separator line to comply. This could probably be done with a regular expression search and replace if desired.

<!-- gh-comment-id:3766583144 --> @DavidAnson commented on GitHub (Jan 19, 2026): You could disable the rule or modify the table to match one of the three supported styles. Your example seems closest to the "compact" style and would only require edits to the separator line to comply. This could probably be done with a regular expression search and replace if desired.
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#778
No description provided.