I/Q: Give names to error codes and align with semantics from JSON RPC spec
Open
enhancement
I/Q
- Dominant language
- Isabelle
- Stars
- 105
- Forks
- 27
- Avg merge
- 12h 45m
- Merged PRs (30d)
- 7
Description
Remove hardcoded error codes such as -32603 from the I/Q implementation. Instead, introduce names for the various error code constants from the JSON RPC spec, and check that they are used as intended by the spec.
Contributor guide
Research direction
Start by locating the I/Q implementation sites that use hardcoded JSON-RPC error codes such as -32603, then consult the JSON-RPC specification for the named codes and their intended semantics. The work is done when the implementation uses named constants and the code paths match the specification's error meanings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100