Skip to content

Flexible url resolving behavior #630

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

Closed
SerikDM opened this issue Nov 8, 2017 · 3 comments
Closed

Flexible url resolving behavior #630

SerikDM opened this issue Nov 8, 2017 · 3 comments

Comments

@SerikDM
Copy link

SerikDM commented Nov 8, 2017

Do you want to request a feature or report a bug?
feature

What is the current behavior?
urls are resolved or not. one global flag via config.

What is the expected behavior?
allow some urls to pass unresolved:
url(media/image.jpg')
url(./media/image.jpg')
url(/media/image.jpg')

some prefix would be great:
url(!/media/image.jpg')

If this is a feature request, what is motivation or use case for changing the behavior?
can't make specific urls that will respect header 'base' meta. root urls do not respect 'base' meta at all.
in case if app hosted in subdirectory like domain.com/forum

@DostalTomas
Copy link

Hello, i've same problem. Adding this feature would be great.
BTW, could you recommend me some workaround for this case?

@michael-ciniawsky
Copy link
Member

This will happen in v1.0.0 (#655)

@michael-ciniawsky
Copy link
Member

#655

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

No branches or pull requests

3 participants