oxidecomputer / oxidecomputer/omicron
project description field ought to be optional
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
$ oxide project create --name testing
error: the following required arguments were not provided:
--description <description>
Usage: oxide project create --name <name> --description <description>
Having a useful description on objects is great, but I don't think it's something you can force. When you don't have one, it would be good to avoid the need to pass the same value for --description as you did for --name (or, something like --description .) just to make the error go away.
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 oxide project create command's argument definition and how it handles project creation. The work is done when --description is no longer required, the command succeeds without it, and the generated help and validation reflect that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100