[GH-ISSUE #315] [MD028] Intended fix is ambiguous, consider removing fix support #268

New issue

Closed

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

kerem commented

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

Owner

Originally created by @yi-Xu-0100 on GitHub (Aug 12, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/315

The problem pointed out the blank line inside block quotes. I used the quick fix provided and found that the fix was to delete the blank line. Whether blank lines can be reserved, that is, use an empty block reference flag, as demonstrated below.

Content before repair:

> Some references

> Some references

Content after repair:

> Some references
>
> Some references

Or give a configuration to set this repair method.

Originally created by @yi-Xu-0100 on GitHub (Aug 12, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/315 The problem pointed out the blank line inside block quotes. I used the quick fix provided and found that the fix was to delete the blank line. Whether blank lines can be reserved, that is, use an empty block reference flag, as demonstrated below. Content before repair: ``` md > Some references > Some references ``` Content after repair: ``` md > Some references > > Some references ``` Or give a configuration to set this repair method.

kerem

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

closed this issue
added the
enhancement

fixed in next
labels

kerem commented

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

Author

Owner

@DavidAnson commented on GitHub (Aug 12, 2020):

Fixes are meant to be simple, unambiguous, and able to be run without the user's involvement. In this case, you make a good point that the right change to the Markdown is not clear and may take either form depending on what the user wishes. Therefore, I'm thinking it may be best to remove the fix behavior for this rule.

@DavidAnson commented on GitHub (Aug 12, 2020): Fixes are meant to be simple, unambiguous, and able to be run without the user's involvement. In this case, you make a good point that the right change to the Markdown is not clear and may take either form depending on what the user wishes. Therefore, I'm thinking it may be best to remove the fix behavior for this rule.

kerem commented

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

Author

Owner

@yi-Xu-0100 commented on GitHub (Aug 13, 2020):

Thanks. I will fix the problem manually next time.

@yi-Xu-0100 commented on GitHub (Aug 13, 2020): Thanks. I will fix the problem manually next time.

kerem referenced this issue

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

[GH-ISSUE #268] Conflicting rules: no-reversed-links and no-bare-urls #2079