ring-clojure / ring-clojure/ring
[stacktrace.clj] Allow condensed stack trace format
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 3.9k
- Forks
- 528
- PR merge metrics
- No merged PRs in 30d
Description
https://clojure.atlassian.net/browse/CLJ-2463
The linked patch to clojure condenses the stack trace to the important line(s). It would be great to see something similar for ring.
Important lines would be the cause and the lines for files in the current app (handler.clj:116 my-app.handler/a-function)
To me this is the most important for the sterr logging. When the error is displayed in the browser, it seems fine to show the whole trace. In the browser it looks like there is some attempt to style less important line with a lighter font. This could be a little easier to read if the same important line(s) were highlighted.
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 with stacktrace.clj and compare the requested behavior with the linked CLJ-2463 patch. Determine how stderr logging differs from browser output and define the important cause and current-application frames to retain or highlight. Done means stderr can show a condensed trace while browser output keeps the full trace and styling distinction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100