Routing pathnames don't allow fragment identifier

[zanzlender]

Hi everyone, first of all I really like the new version, and I didn't have any complaints until this case.

I wanted to internationalize both my path names and fragments ids.

E.g. I have a link to;

• /services#service-1

The problem is if I define my pathnames as just services, when passing my full url to the href of the Link compnent it says it's incorrect.

If I just ignore the error, the app still works but after rewrite, my fragment is not visible.

My current workaround is to define all possible fragments as pathnames, but I think this needs improvement.

Any takes?

[amannn]

Fragments can unfortunately not be rewritten by the middleware since they are not transferred to the server. #service-1 is only known to the browser that's opening the link.

What you could do however is saving your fragments in translations and use them for your section IDs as well with the routing APIs that might link to them.

[zanzlender]

yes, that's how I'm doing it right now. The problem is if you want to use translated pathnames as well... Since the Link component validates that the href is /services, if it's defined like that in pathnames, it doesn't allow me to something like:

<Link href={`/section${t("section_1")}`}></Link>

[amannn]

You can pass the fragment separately:

<Link href={{pathname: '/section', hash: t('section_1')}} />

[zanzlender]

oh damn, I didn't know you can do this. Thank you, I'm all set now 😎