-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
pagePerSection links break when section name includes a "/" #1332
Comments
pagePerSection
links break when section name has includes a "/"
Feel free to send a pull request with a fix. |
If you have a forward slash in your section name, the pagePerSection links are all broken, resulting in "Page not found". Removing the forward slashes in the names fixes the issue. For example: pagePerSection links break when section name includes a "/", like `name: '@foo/components'` Solution is just encode name in the getUrl and then correctly decode it in the router logic. iss: styleguidist#1332
🎉 This issue has been resolved in version 9.1.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This appears to have fixed the top level section link, but any sub-links within that section are still unencoded and result in "Page not found". |
@stonebk could you please give an example of the config file to get an exact idea of sub-links you are talking about? |
@mendrew it looks something like this:
With that config, both the "Components" link under the section name, and all the links under "Components" have unencoded urls. |
Awesome, thank you, I'll take a look. |
Follow up of styleguidist#1332 This appears to have fixed the top level section link, but any sub-links within that section are still unencoded and result in "Page not found".
Follow up of #1332. This appears to have fixed the top level section link, but any sub-links within that section are still unencoded and result in "Page not found".
@mendrew, all better now! Thanks so much! |
Awesome, you're welcome! 🙂 |
Current behavior
If you have a forward slash in your section name, the
pagePerSection
links are all broken, resulting in "Page not found". Removing the forward slashes in the names fixes the issue.To reproduce
Simple
styleguide.config.js
:Expected behavior
Links should work for any text in a section name field. Probably just need to urlencode the string.
The text was updated successfully, but these errors were encountered: