cloudfoundry / cloudfoundry/cloud_controller_ng
**Charter:** Find places where the **API returns errors** due to **uniqueness** constraints
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Follow up to https://www.pivotaltracker.com/story/show/169001680 and https://www.pivotaltracker.com/story/show/173478178
Objective: PM can write stories to expand usage of NotUniqueError to all relevant endpoints.
Method: Explore the API source code to find other cases that return errors about a resource already existing and/or not being unique.
Deliverables:
- Write up a list of cases in whatever format is easiest.
- (Optional) Suggest how to chunk these endpoints together into stories. Should there be a story for every endpoint? Every resource? One giant story?
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 exploring the API source for cases where resources already exist or are not unique, and compare them with existing NotUniqueError usage. Record each relevant endpoint and resource in an easy-to-share list; the work is done when the cases are documented and optional groupings into follow-up stories are suggested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100