[Feature?]: File-based routing for middlewares
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 426
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Summary 💡
Middlewares that run only on a given route, with file-based routing. The file rules would be similar to those of a layout that works on all routes of a given directory.
A good example can be seen in the Fresh framework, this is a good reference of the feature:
https://fresh.deno.dev/docs/concepts/middleware
Examples 🌈
No response
Motivation 🔦
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Fresh middleware documentation linked in the issue, then locate SolidStart's existing file-based routing and layout handling entry points. Define how route-scoped middleware should be discovered and composed, and verify that middleware files apply only to the intended routes without changing broader layout behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100