Make error codes from Access API more intuitive
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 361
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
Instructions
Please fill out the template below to the best of your ability and include a label indicating which tool/service you were working with when you encountered the problem.
Issue To Be Solved
One of the feedback from the Flow hackathon was that the "Error codes from Access nodes were unintuitive". This issue to investigate how the Access API errors code can be improved.
(Optional): Suggest A Solution
(Replace This Text: A concise description of your preferred solution. Things to address include:
- Details of the technical implementation
- Tradeoffs made in design decisions
- Caveats and considerations for the future
If there are multiple solutions, please present each one separately. Save comparisons for the very end.)
(Optional): Context
<what are you currently working on that this is blocking?>
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 by locating the Access API and Access-node error-code definitions and their callers in the Go repository; the issue names no files or tests. Determine which codes users found unintuitive and agree on an improved, consistent mapping before implementation. Done means the revised error-code behavior is implemented and verified by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100