[v7] Two routes leading to the same file?

[tomekbuszewski]

Hey folks,

I have a peculiar problem, namely, I have a centralized content handled by a hook. So basically I set the language once in the context and then the translate hook is using it to decide which translation database it should query.

What I want is to have distinct urls: /en/whatever, /pl/whatever etc. I've solved it using prefixes:

(...)
    ...prefix("/pl", [
      index("pages/pl/home.tsx"),
      route(Routes.website, "pages/pl/services/web-development/index.tsx"),

But the problem is, it has to lead to a different file. Right now I am simply reexporting things inside /en/.tsx and /pl/.tsx, but this is quite poor solution.

What can I do to have both prefixes leading to the same file?

[GabenGar]

Write a loader/action factory which resolves the locale from the URL and passes it as a parameter to the parameter function.
And yes, it does mean you'll have to call it in literally every page which is a subpage of the the locale segment, but such is the internationalization life.

[sergiodxa]

Why not make the prefix a param?

route(":locale", "pages/locale.tsx", [
  index("pages/home.tsx"),
  route("something-else", "another-file.tsx")
])

Then in your routes params.locale will be the correct locale, and in pages/locale.tsx you can check if the locale is in a list of valid locales otherwise redirect to the URL with the default locale.