typelevel / typelevel/natchez-http4s
Trace 404
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 50
- Forks
- 18
- Avg merge
- 15m
- Merged PRs (30d)
- 5
Description
Currently server middleware is defined on HttpRoutes so it has to be applied before .orNotFound and it would not run if route is not found.
I think it should default to HttpApp with HttpRoutes provided as an alternative for more complex integrations.
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 examining how server middleware is currently applied to HttpRoutes before .orNotFound. The change is complete when middleware defaults to HttpApp, retains HttpRoutes as an alternative for complex integrations, and tracing also covers requests that result in 404 responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100