redpanda-data / redpanda-data/console
Improve how backend errors are shown
Open
Nobody has claimed this yet.
backend
frontend
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 432
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 40
Description
This isn't nice:
Instead, we should
- not emit the same error multiple times (maybe just parse/compile once first, and if that fails return, instead of letting each consumer compile the code itself and then have them report the error separately)
- collect errors in the frontend and have a proper "collection"/"log" where the user can view the errors and clear them (because there are some legitimate scenarios where multiple errors might be returned).
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
No files, tests, or entry points are named. Start by tracing where backend errors are emitted and where the frontend displays them, then determine how duplicate errors and legitimate multiple errors should be represented. Done means repeated errors are not emitted separately and users can view and clear the collected errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- backend, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100