Better handling of caught ExceptionInfo objects
Open
Nobody has claimed this yet.
client
enhancement
- Dominant language
- Clojure
- Stars
- 323
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
We could use (ex-data) et al. to produce a nicer message than what (pr-str) gives. Also the stack trace for them isn't particularly useful.
Contributor guide
No contributing guide indexed for this repository
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 locating where caught ExceptionInfo objects are formatted and where their stack traces are produced. Compare the current pr-str output with the available ex-data information, then verify that the resulting message and stack trace are more useful.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100