-
Notifications
You must be signed in to change notification settings - Fork 207
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
Broken relative links #112
Comments
Thanks for pointing out the broken link. In We are discussing right now and coming up with a plan. If a patch release is required, we can implement the fix and make a new release quickly. I will keep this thread up to date. Thanks again for letting us know about this issue. UPDATE: The broken |
We are in the process of improving the logic Retype uses to resolve links. Once complete, the original scenario will be resolved correctly. The plan is to include this bug fix (or is it an enhancement? 🤷) in a |
This issue has been fixed and the fix was included in Hope this helps. |
I'm not very familiar with front-end stuff, but from what I see, relative links (to "parent directory") are broken. Maybe dynamic link substitution will solve this?
Example found on your very docs:
../components
should in theory lead toretype.com/components
, but leads toretype.com/guides/components
(There's a resolved link shown at left bottom corner)
P.S. If such behaviour as relative links shouldn't exist, at least fix this particular link please :D
The text was updated successfully, but these errors were encountered: