InseeFrLab / InseeFrLab/extract-table-ui
Deal with error handling after API calls
Open
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Custom messages should be displayed on the app instead of errors when API calls did not yield successful results.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the API call handling and the app's error-rendering entry points, then trace how unsuccessful responses reach the UI. Done means failed API calls consistently show custom user-facing messages instead of raw errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100