Error response
Open
good first issue
- Dominant language
- TypeScript
- Stars
- 44
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Dear Kata team,
Can we have more detail in error response,
so more clear in error result instead of just "Bad Request"
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the CLI's error-handling entry point and reproduce the response that currently reports only "Bad Request." Trace where the underlying error information is discarded; done means errors provide more detail in the CLI response, with coverage added for the resulting output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100