[Feature Request] Checking Space around Embedded Code, Bold and Italic

[fyc09]

Adding spaces around embedded code, bold, and italics is common practice to prevent unexpected rendering errors and make words recognizable. While Chinese can be recognized without spaces, adding spaces can enhance clarity and readability.

Correct:

some *important* point
some `inline` code
一些 *重要* 的信息
一些 `inline` 代码

some important point
some inline code
一些 重要 的信息
一些 inline 代码

Incorrect:

some*important*point
some`inline`code
一些*重要*的信息
一些`inline`代码

someimportantpoint
someinlinecode
一些重要的信息
一些inline代码

[fyc09]

@DavidAnson Can we use micromark as the parser in customRules to simplify column calculations?

markdownlint/lib/markdownlint.js

Lines 58 to 66 in b2305ef

	if (
	!result &&
	(rule.parser !== undefined) &&
	(rule.parser !== "markdownit") &&
	!((customIndex < 0) && (rule.parser === "micromark")) &&
	(rule.parser !== "none")
	) {
	result = newError("parser", rule.parser);
	}

[DavidAnson]

Not yet. I want to convert the remaining core rules to micromark first, then review the API. Custom rules can still use markdown-it and the "helpers" package, but I am slowly removing things from that as I migrate, so feel free to use or copy from earlier versions.

[Faker095]

if (
!result &&
(rule.parser !== undefined) &&
(rule.parser !== "markdownit") &&
!((customIndex < 0) && (rule.parser === "micromark")) &&
(rule.parser !== "none")
) {
result = newError("parser", rule.parser);
}

[DavidAnson]

@fyc09, i'm not sure what the comment above is saying, but to get back to your question from six months ago, it is now possible to write custom rules that use the micromark parser. As you say, the line/column information should be easier to work with in that form. If you have any trouble, please let me know!