-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Markdown linting and use it on more files #4515
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mdv
is still listed independencies
: can we remove it?markdownlint-cli2
is not declared as a dependency,devDependencies
still lists the traditionalmarkdownlint-cli
that we used before
The It also calls
|
@@ -1,14 +1,16 @@ | |||
# Technical Oversight Board ("TOB") | |||
|
|||
## Description: | |||
## Description | |||
> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> |
Empty line after headline instead of block-quoted empty line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good direction, let's just remove mdv
everywhere.
Fixes #4249 which asks for Markdown linting to be applied to the markdown files at the root level of the repo.
Points to look for:
mdv
, it is outdated and we can do most of what's needed with markdownlint. My only concern is that we're missing some formatting of json/yaml/abnf code examples, so we should consider any options on that (and be careful with them in the meantime!)sed
manouvre to fix it. I don't think the benefits of using prettier are worth having this sort of hackery in the project so we'll use the markdownlint "fix" feature instead and I removed the script.I realise that
src/oas.md
isn't present on this branch but the same configuration seemed to be okay with what's currently on bothv3.1-dev
andv3.2-dev
.