You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Links can be ignored in many different ways, including with --include, --exclude and .lycheeignore. However, sometimes, it would be nice to ignore only one specific link in a given file.
A common way to do this is often to add a comment like <!-- lychee-disable-next -->, like markdown-link-check does, ESLint, and so on.
One challenge is that those comments would be file format-specific. Other tools often opt to only implement this for Markdown, but there might be some creative solutions to make this format-agnostic.
I checked the issues and I do not think this has been asked before. What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
As you said, we would need to handle various file formats, making the tool more complex and harder to maintain.
For instance, markdown-link-check also has edge-cases like .mdx support (tcort/markdown-link-check#171) or anchor links (tcort/markdown-link-check#196).
--exclude and .lycheeignore should support that already, no? For example, instead of annotating a link in a file, why not add it to .lycheeignore?
Links can be ignored in many different ways, including with
--include
,--exclude
and.lycheeignore
. However, sometimes, it would be nice to ignore only one specific link in a given file.A common way to do this is often to add a comment like
<!-- lychee-disable-next -->
, likemarkdown-link-check
does, ESLint, and so on.One challenge is that those comments would be file format-specific. Other tools often opt to only implement this for Markdown, but there might be some creative solutions to make this format-agnostic.
I checked the issues and I do not think this has been asked before. What are your thoughts on this?
The text was updated successfully, but these errors were encountered: