cloudfoundry / cloudfoundry/stratos
Handle Generic 4XX errors
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Wire in 4XX errors to existing error handler
- 4XX errors should not appear in red error bar but should be listed in error page
- 4XX errors should be shown in snack bar with link to error page
- For example, on cf org lists if delete org fails there's no feedback to user
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
Start by locating the existing error handler, error page, snack bar, and the CF organization list flow. Trace a failed organization deletion and verify that generic 4XX responses are listed on the error page, linked from a snack bar, and excluded from the red error bar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100