Support for rewrites of routes

[thomasverleye]

Let's say you have these routes available in your routes folder:

routes
│   companies.tsx
│   records.tsx 

Routes explained:

• The /companies url is a view of all companies on the platform only available as users with an admin role.
• The /records url is a view for the companies to see their "records".

If I want to be able to give the admin the ability to see and edit all records from a specific company, I will have to create this folder structure:

routes
│   companies.tsx
│   records.tsx  
│
└───companies
│   │   index.tsx
│   │
│   └───$companyId
│       │   records.tsx

New route explained:

• /companies/$companyId/records view of the records of a specific company.

In the ~/routes/companies/$companyId/records.tsx I will have a sourcecode like this:

import Records from '~/routes/records';
export * from '~/routes/records';
export default Records;

This is a redundant workflow to enable this route.
You can imagine that later on when extra routes are added for the companies that have to be viewable for the admin this will be a lot of these files.

I was wondering if something similar as "rewrites" in Next.js is on the roadmap for Remix?
Or did I misread something in the docs and is this already possible in some way?