Allow mixing localized pathnames and unknown routes

[oskari]

Is your feature request related to a problem? Please describe.

We have an app that uses both localized pathnames for few static paths but rest of the routes are handled by our CMS. We handle our routes with src/app/[locale]/[[...slug]] app router path, but we want to define few routes in the config, eg.:

export const routing = defineRouting({
  locales: ['en', 'es'],
  defaultLocale: 'en',
  localeDetection: false,
  localePrefix: "as-needed",
  localeCookie: false,
  alternateLinks: false,

  pathnames: {
    "/route-example/[slug]": {
      en: "/some-static-route-path/[slug]",
      es: "/some-static-route-path-in-es/[slug]",
    },
    "/another-path/[slug]": {
      en: "/static-route/[slug]",
      es: "/static-route-es/[slug]",
    },
  },
})

but this doesn't seem to be possible, as redirect expects the href to be on of the pathnames defined, when it should be string | pathnames ?

Describe the solution you'd like

Allow mixing localized paths and unknown routing

Describe alternatives you've considered

We've currently had to resort on using our own middleware to handle localized paths

[amannn]

I think you could probably add [[...slug]] to the pathnames config to allow arbitrary slugs in addition to a few known pathnames.

I'll move this to a discussion since it's a usage question.

[oskari]

Do you mean like this way?

pathnames: {
    "/[[...slug]]": {
      en: "/[...slug]",
      es: "/es/[...slug]",
    },
    ...
  },

At least redirect still seems to expect literally the same string as defined in pathnames

Am I missing something?

[alexclinky]

Is there a catch all example, cause i dont want all my pathnames translatable yet i dont want to enter all pathnames to not be translated