softwaremill / softwaremill/tapir
Improve error reporting in the tapir-upickle integration
Open
Nobody has claimed this yet.
Pickler
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 468
- Avg merge
- 5h 37m
- Merged PRs (30d)
- 34
Description
Both in the "standalone" mode and in pickler. Maybe this can be done optionally by adding the trace = true parameter to the read invocation, and then properly translating the exception.
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 the tapir-upickle integration and the read invocations used by both standalone mode and pickler. Compare how each path reports failures, then verify that an optional trace setting and translated exceptions produce clearer error messages in both modes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100