influxdata / influxdata/influxdb
Better error handling
Open
team/ui
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
There are a number of places where we do not display the error we get back from the API. This can be confusing to end users. It would be great to have a wholistic approach to how we handle errors in the front-end.
Contributor guide
Research direction
The issue does not name any files, tests, or entry points. Start by mapping the front-end paths that handle API responses and identifying where errors are currently omitted; done means API errors are displayed consistently across the relevant paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100