chore: introduce @eslint/markdown and eslint-plugin-markdown-preferences
#2913
+177
−69
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
FloEdelmann
reviewed
Aug 4, 2025
FloEdelmann
added
the
meta
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces
@eslint/markdownandeslint-plugin-markdown-preferencesto the repository.We prefer to have links in rule names in release notes and changelog, and this PR will allow the
markdown-preferences/prefer-linked-wordsrule to automatically detect and fix that.https://ota-meshi.github.io/eslint-plugin-markdown-preferences/rules/prefer-linked-words.html
After merging this PR, I believe the
changeset:versionscript should automatically include the link without having to include it in the changeset file.