cloudfoundry / cloudfoundry/stratos
Endpoints + Routes + instances: Wire in multi unregister
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
From @richard-cox on January 8, 2018 14:25
Copied from original issue: SUSE/stratos#98
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 existing unregister flows for endpoints, routes, and instances in the TypeScript UI. Determine how each flow handles one item and where multi-selection is represented. Done means the multi-unregister behavior is wired consistently across these three areas and verified against the existing project checks.
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
- 25/100