Way to keep a route active while preventing it from being used?

[allan-cannon]

TL;DR - Is there a way to keep a route path functionally active for backwards compatibility while also removing it from the Typescript path definitions so it doesn't get accidentally used in the future?

I recently refactored some routes in a way that is basically a rename, e.g. foo/$id/summary -> bar/$id/summary. I removed all navigation to the old routes and added redirects to the old route definitions. That's great but the old routes still appear as valid routes with Typescript.

Is there a good way to prevent that while still maintaining backwards compatibility with the routes?

[schiller-manuel]

what would "preventing" mean here? cause a TS error?

[allan-cannon]

Yes, cause a TS error and not suggest deprecated paths in intellisense.

[schiller-manuel]

so these old routes now only contain a redirect? or is there more inside

[allan-cannon]

Just redirect. Something like:

export const Route = createFileRoute('/foo')({
  beforeLoad: () => {
    throw redirect({ to: '/bar' });
  },
});