Create a more regular API with clear return codes and error messages
Open
enhancement
H𝗜𝗚𝗛
- Dominant language
- APL
- Stars
- 26
- Forks
- 11
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 1
Description
with accessible backlog, to check for errors over a working session.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name any files, tests, or entry points, and its body only mentions checking errors during a working session. Start by locating the public API and its existing return and error conventions. Done would require an agreed, consistent API shape with documented return codes and error messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100