cloudfoundry / cloudfoundry/stratos
Apply new maxed process to all collections
Open
Nobody has claimed this yet.
scalability
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Step 1 - Apply to all lists
- Step 2 - Apply to all collections (for instance where we fetch all results for validation purposes, if the collection is maxed need to handle error)
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 maxed-process implementation and the code paths that fetch lists or collections for validation. Trace how maxed collections currently behave, then confirm that all lists and collections handle the maxed condition consistently, including the error case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100