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
I have an internal link checker (written in Common Lisp) and it's been a real challenge to get my internal documentation to pass with no bad links. There are many, many false positives. Why? Because of the breadcrumbs. They look like this:
What's wrong is that /readme/agraph really should be /readme/agraph/, because when the base URI without the slash is merged with a document, say, foo.md, then it will produce /readme/foo.md instead of /readme/agraph/foo.md.
In all other places, the trailing slash is included.
It would be extremely helpful (I don't know how to workaround this in the link checker) if the trailing slash could be included. In this case, you know that the breadcrumbs are directories so including the trailing / is always the right thing.
Thank you.
The text was updated successfully, but these errors were encountered:
Does that mean we can choose another config to work around this? I looked at the docs and didn't see anything about a config option to change and what the allowed values might be for it.
I have an internal link checker (written in Common Lisp) and it's been a real challenge to get my internal documentation to pass with no bad links. There are many, many false positives. Why? Because of the breadcrumbs. They look like this:
What's wrong is that
/readme/agraph
really should be/readme/agraph/
, because when the base URI without the slash is merged with a document, say,foo.md
, then it will produce/readme/foo.md
instead of/readme/agraph/foo.md
.In all other places, the trailing slash is included.
It would be extremely helpful (I don't know how to workaround this in the link checker) if the trailing slash could be included. In this case, you know that the breadcrumbs are directories so including the trailing
/
is always the right thing.Thank you.
The text was updated successfully, but these errors were encountered: