Is there a way to bypass the base of the Router in a Link?

[jeerbl]

I tried <Link href="~/path">...</Link> but the ~ does not seem to bypass the base of the router. On top of that, when specifying an HrefFormatter to the router to bypass manually in the Router configuration, the ~ character is not included in the link.

Is there any other way to achieve this? Let me know if this need more clarification.

Jérôme

[molefrog]

Hi @jeerbl, could you share a piece of code? This is supposed to work.

[jeerbl]

Hi @molefrog, I made a CodeSandbox. I've actually seen something strange, looking deeper into the problem.

What I'm trying to do is to have the same component in two different contexts, go to the same URL, and Wouter actually does, but the href set on the <a> element is for some reason wrong and different than the path Wouter actually navigates to.

In that example, if you access /sub/url, you'll see the link prefixed with ~ go to the actually root URL /url. When you're in /url, the <Link> still goes to /url (which is what I want), but the URL displayed in href attribute of the <a> element is actually /sub/url.

First thing is, what should happen here in my opinion is to have the <a> href element to be the same as where Wouter navigates to.

Second thing is, should Wouter actually ignore the hrefs when navigating? Is this what's expected? It benefits my case but I'm not sure if that's what's expected here.

[molefrog]

but the URL displayed in href attribute of the <a> element is actually /sub/url.

That's because you have a custom hrefs formatter, if you remove it you the href will be /url isn't that something you want?

[molefrog]

The hrefs only affects the href attribute rendered and it is mostly needed for server-side rendering (e.g. when you use hash-based routing, the html rendered must be <a href="#/" /> and not <a href="/" />). It does not affect the actual client-side navigation.

[jeerbl]

I see, thank you. So just formatting and nothing else.

Closing this.

[jeerbl]

Actually reopening this for advice. I updated the CodeSandbox.

Here, in this new piece of code, the component LinkComponent is going to /url so, in the <Router base="/sub"> this link will be /sub/url and in the first <Router> line 17, it will go to /url.

My question is—if I want the LinkComponent to always go to /sub/url, even when used on line 17, what would you suggest?

I would want all links under the <Router> line 14 to always add /sub to the route.

[molefrog]

My question is—if I want the LinkComponent to always go to /sub/url, even when used on line 17, what would you suggest?

Just use ~/sub/url. The base path for default router is always /

[molefrog]

Hi @jeerbl is this issue still relevant?

[jeerbl]

Hi @molefrog, actually it isn't! Closing this issue :)