oxidecomputer / oxidecomputer/console
make sure descriptions can't consist of only whitespace
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
It's possible, when creating an IP Pool, to add a description consisting of (a single space). We should run trim() on the description at create/update time, to make sure than an empty description doesn't get passed through.
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 IP Pool create and update entry points and tracing how the description is submitted. Check the existing validation or form tests, if present, and verify that whitespace-only descriptions are not passed through while non-empty descriptions continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100