Improve Respect error logging
Open
Nobody has claimed this yet.
Respect
Type: Enhancement
Type: Maintenance
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 228
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 48
Description
Is your feature request related to a problem? Please describe.
Currently, the network error in Respect doesn't contain info about the error code.
Describe the solution you'd like
The output should contain enhanced error message (at least the error message code).
The exact format to be discussed (@sobanieca-redocly, @DmitryAnansky).
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
The issue names no files or tests. Start by locating Respect's network error handling and inspecting how the current error output is assembled. The work is done when the output includes the error code and the exact message format has been agreed with the maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100