Baseflow / Baseflow/flutter_cache_manager
Provide response body for status code 400
- Langage dominant
- Dart
- Étoiles
- 809
- Forks
- 510
- Merge moyen
- 6 min
- PR mergées (30 j)
- 1
Description
## 🚀 Feature Requests
Fetch and provide response body for certain error status codes.
### 🎤 Pitch
Many APIs provide further information in the response on bad client requests (status code 400)
This allows to forward that information to the user in order to explain what he did wrong.
Sadly, since flutter_cache_manager handles all errors equally by discarding the response contents, that information is lost, only allowing us to show a generic "invalid request" message.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
No files or tests are named. Start by tracing how flutter_cache_manager handles HTTP errors and discards response contents; verify the behavior with a 400 response that contains a body, and consider the work done when callers can access that information instead of only a generic error.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- dart, flutter
- Domaine
- api, backend
- Type d'issue
- Fonctionnalité
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100