Improve Error Handling by proving path to error in JSON.
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 360
- Forks
- 113
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 4
Description
It would be very helpful to get the path in the json provided to where the error is coming from.
e.g. when I pass a number where there should be an object, I get the error: "applyeach not applicable for JSON.LazyValue{String} with JSON type = JSONTypes.NUMBER".
(if I pass "percent": 0.1 instead of "percent": {"value": 0.1})
It would be much better, if a path to the error is added, like "applyeach not applicable for JSON.LazyValue{String} with JSON type = JSONTypes.NUMBER at /path/to/percent ".
Thanks!
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 applyeach error path in JSON.jl and trace how the current JSON location is handled while nested values are processed. Add the failing value's path to the error message, then verify that the example with percent as a number reports the path to percent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100