Add markdownlint extension
#279
Merged
Conversation
This file contains 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
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.
Description & Motivation
DEPENDS ON #277
RELATED TO #280
It is suggested to add the extension for VSCode to the list of those installed in the container (
./devcontainer/devcontainer.json) and the list of recommended ones (.vscode/extensions.json). The extension should make it easier to follow the established rules when working with Markdown.Related Issue(s)
No.
Testing
Clone branch, open in VSCode, get suggestions for installing extensions.
Backwards-compatibility
No.
Documentation
This can be mentioned, for example, in
README.md, but these changes are not included in this PR.