-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: html anchor support #5
Conversation
We don't need to check if fragments are valid in own file. It's already checked by the rule MD051 of markdownlint (else we have the error duplicated). Ref: https://github.com/DavidAnson/markdownlint/blob/main/doc/md051.md
Thank you for your PR, it is highly appreciated! 😄 Note about
|
🎉 This PR is included in version 2.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@theoludwig Thanks, awesome collaboration! |
What changes this PR introduce?
Plugin now recognizes links to anchors, either by id or by name. I tried to stick to the way markdownlint does that, so borrowed a helper to extract the anchor attribute from there.
List any relevant issue numbers
Addresses #4
Is there anything you'd like reviewers to focus on?
Had some issues with passing the commit checks. I am not very familiar with JS ecosystem, so resolved them the way I could. Feel free to propose a better solution.
tsc
like:so excluded
node_modules
injsconfig.json
Removing
./test
from node command fixed that, maybe that is due to my node version is newer?tsc
:Perhaps this is because this function has only been recently introduced to
markdownlint-rule-helpers
and the corresponding@types
has not been yet updated. I figured since there is no TS used anyway I would fix this with@ts-ignore
.