chore: optimize readme #81
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
`rule.to` or `rule.name` are being converted to links by [markdown-it/linkify-it](https://github.com/markdown-it/linkify-it). Let's fix it here instead of the docs (I couldn't find a simple enough fix in the docs for it).
Turns out wrapping the headings in backticks disables `linkify-it` 🤠
Playwright test results
Details
|
2 tasks
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
Today I noticed that on the docs page of fragment plugin there were a few broken headline links. Turns out that this was caused by
markdown-it/linkify-it, that considered bothrule.toas well asrule.nameto be URLs.Wrapping those in backticks disabled the falsy linkification.
Drive-By
Checks
masterbranchnpm run lint)