-
Notifications
You must be signed in to change notification settings - Fork 150
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
Add link to root directory #23
Comments
I'm not sure if |
Yea I just chose the tilde cause nothing else really fit. The apache variant doesn't include a breadcrumb. If you want some examples just google "mp3 apache index of". We could recycle one of the icons and serve that instead? |
Ooo, good idea!
You mean use an icon for that path component? That could probably work. My only other thought was a ".", which is so tiny and probably no one would notice, or maybe a word? I do agree we should add the root link, though :) Just trying to think of a good way to fit it in. |
Yea a word seems simple enough, maybe, "root", "index", or something like that. Also, what the name of the root folder? So if you're serving from In regards to icons, If you checkout the breadcrumbs on the apple site, they use their logo as the to go to the home page. So using an icon their isn't totally unacceptable. |
How about we just use |
It doesn't get forgotten :) Issues like this stay in my inbox until they are resolved. We'll probably simply use an image. Perhaps |
Yea |
lol, I'm just going to use |
lol. Cheers |
Published as 1.6.0 |
Currently, the
htmlPath
function correctly returns a series of links to child directories of a resource, but it does not provide a link to the "root" folder.For example. Given you have navigated to
"/foo/bar"
, the following html is created:Would you guys be open to a PR that would simply prepend the following
"<a href="/">~</a>"
to what is being returned byhtmlPath
so as the generated html would look like this:This way there is a quick link back to the root folder of the directory that is being served.
The text was updated successfully, but these errors were encountered: