-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Breadcrumbs are problematic #174
Comments
The relevant code is here: madness/lib/madness/breadcrumbs.rb Line 31 in c333a01
I will see if adding the trailing slash to all breadcrumbs hrefs works without breaking anything. |
This is solved in the master branch and edge version. |
Version 1.2.0 is now released with this fix. |
@DannyBen thanks for the fix! However, we're having issues testing the new release:
|
Btw, this is using your docker image: https://hub.docker.com/layers/dannyben/madness/1.2.0/images/sha256-4869e3523427a3ddd877f04b73a893b77d6f976811bf6569ac292d1b6e058acd?context=explore |
You seem to be using a custom theme, am I right? If so, use the original theme first or copy the breadcrumbs template, since it has changed. |
@DannyBen That was it. Thank you so much! |
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.I figured the fix would be pretty easy, but when I did
git grep -i breadcrumbs
it had no hits. So, maybe the real bug is in a dependent project?Thank you.
The text was updated successfully, but these errors were encountered: