Skip to content
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

Relative links not always identified #218

Open
jedthehumanoid opened this issue Jan 9, 2022 · 1 comment
Open

Relative links not always identified #218

jedthehumanoid opened this issue Jan 9, 2022 · 1 comment

Comments

@jedthehumanoid
Copy link

jedthehumanoid commented Jan 9, 2022

Bear with me if I have misunderstood usage.

I feel like a common usage is having images that look like this:
![](image.png)
which references current directory.

Now if I want to prefix that in html, so that it points to /public/ or something, my solution was to use

RendererOptions{
	...
	AbsolutePrefix: "/public/",
}

Which does not seem to work.

Digging a little bit shows that isRelativeLink()-function says that it's not relative
Isn't it though? 🙂

AFAICT, it's proper syntax for relative urls, and quite commonly used.

Would you be open for a pull request, adding some more heuristics to isRelativeLink()?

@jedthehumanoid
Copy link
Author

jedthehumanoid commented Jan 9, 2022

Seems like I can probably solve this with a custom RenderNodeHook otherwise?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant