-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Fix #865 #867
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
Fix #865 #867
Conversation
Addresses #865 |
All reactions
-
🎉 1 reaction
Sorry, something went wrong.
We need to add tests first in this project then we will check if it's breaking or conflicting any other links |
All reactions
Sorry, something went wrong.
Hi all, I am also experiencing this issue. BR, |
All reactions
Sorry, something went wrong.
@aenniw please rebase and resolve the conflicts. |
All reactions
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please rebase to run the tests.
else it looks good to me
Sorry, something went wrong.
All reactions
d55c5ba
to
14c0688
Compare
Signed-off-by: Martin Mihálek <aenniw@gmail.com>
Rebased |
All reactions
Sorry, something went wrong.
Still happened in 4.11.2, example: links in https://jack-works.github.io/bayesian-conspiracy/#/./projects/2019/holoflows-kit.md |
All reactions
Sorry, something went wrong.
anikethsaha
Successfully merging this pull request may close these issues.
Embedded files doesn't resolve relative links
fixes #865
Signed-off-by: Martin Mihálek aenniw@gmail.com
Summary
Added relative to absolute path resolving in embeded mardown files for links like so:
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
lib
directory.