-
Notifications
You must be signed in to change notification settings - Fork 4
Internal page routing is not configured correctly #3
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
Comments
Weird, I'll look this up right now. Also, I'm gonna add you as a repo collaborator so it's easier to add more stuff that's missing if I miss the PRs (I don't get the notifications for this repo for some reason even if they're enabled) |
It looks like docsify always starts the research of the file from the projects root, so to access a file in the dev directory from the dev directory again, we have to do
|
Fixed it, now relative paths are used instead (as it should have been from the start): # from bootloader.md in dev/
[Testpoints](testpoints.md)
# from testpoints in dev/
[Bootloader](bootloader.md) |
I noticed lol, looks like relatives links impact the sidebar too, even tho it lives in the root |
I'll have to make a different sidebar for every directory, or even better: find a way to make the sidebar ignore relative links |
Seem to be an issue from docsify itself: I'll make different sidebars for every directory so that we can still use relative paths |
@progzone122 does it work now? |
sidebar fixed |
Routing similar links (which are not in the sidebar) to internal resources does not work correctly.

It seems that this needs to be configured, for example, as in the same React, Vue, etc.
The text was updated successfully, but these errors were encountered: