cloudfoundry / cloudfoundry/stratos
Wire in general jetstream + github error handling to the internal events mechanism
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Where appropriate
- Can handle errors such as system info failures
- Should not cover modals
- CF errors cannot be done until #2083 is completed
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 tracing the internal events mechanism and the general Jetstream and GitHub error-handling paths mentioned in the issue. Check how system-info failures are represented, while keeping modal errors out of scope and deferring Cloud Foundry errors until #2083. Done means applicable errors reach internal events without covering modals or blocked Cloud Foundry cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100