cloudfoundry / cloudfoundry/stratos
V3 API: Handle new single endpoint for service instances and user provided service instances
Open
Nobody has claimed this yet.
v3 api
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- service instance wall can be much simplified
- need to determine which card to show given content of entity (there should be a flag)
- see https://docs.google.com/document/d/1P5laZqVYjtl_boSdpksT5LHOFjhm6CQLzWVx24UpXpM/edit#heading=h.wjh8gfo4d6fd
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 with the linked design document, then trace the V3 service-instance entry points and the service instance wall. Determine how the entity content indicates which card to show and confirm the wall can use the single endpoint for both service instances and user-provided service instances. Done means the endpoint and card-selection behavior match the design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100