Please the Markdown Linter via Cleanup. #44
Conversation
FSG-Cat
force-pushed
the
FSG-Cat/markdown-lint
branch
from
e8ac2e1 to
7e5a3c0
Compare
FSG-Cat
force-pushed
the
FSG-Cat/markdown-lint
branch
from
f9089c3 to
1e43478
Compare
| mjolnir from the JavaScript Debug Terminal using `yarn test:manual`. | ||
| This will launch mjolnir using the config found in `config/harness.yaml`. | ||
| You can now open https://app.element.io, change the server to `localhost:8081`, | ||
| You can now open [https://app.element.io](https://app.element.io), change the server to `localhost:8081`, |
There was a problem hiding this comment.
| You can now open [https://app.element.io](https://app.element.io), change the server to `localhost:8081`, | |
| You can now open <https://app.element.io>, change the server to `localhost:8081`, |
There was a problem hiding this comment.
Quick way to trigger a build failure. I did exactly this before and it triggers a build failure.
There was a problem hiding this comment.
<link> isn't valid commonmark last I checked.
There was a problem hiding this comment.
The markdown linter thought it was fine but Docusaurus wont think that and will trigger a build failure.
There was a problem hiding this comment.
<link>isn't valid commonmark last I checked.
It's valid commonmark. Search "autolink" in spec. Iirc it's even only part of commonmark and not others.
There was a problem hiding this comment.
The markdown linter thought it was fine but Docusaurus wont think that and will trigger a build failure.
Smells like they parse mdx rather than commonmark markdown 👀
There was a problem hiding this comment.
By default, Docusaurus v3 uses the MDX format for all files
FSG-Cat
force-pushed
the
FSG-Cat/markdown-lint
branch
from
4aaf60c to
baf1861
Compare
4 participants
This PR pleases the markdown linter via a general cleanup of errors it found. Tho if a error in its regards is invalid as far as im concerned its ignored.