oxidecomputer / oxidecomputer/console
Better name taken message than "name already exists"
Open
Nobody has claimed this yet.
polish
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
This is both vague and weird. Names are unique within their parent scope, so ideally we would find a way to say "There is already a disk with that name in the project", "There is already a rule with that name in this VPC", etc.
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 where the console produces the "name already exists" message, then trace the create flows for resources such as disks and rules. Identify what parent-scope information is available in each case; done means the message identifies the conflicting resource and its scope instead of using the vague wording.
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
- Mostly clear
- Newbie friendliness
- 45/100