manifoldco / manifoldco/torus-cli
Style guide - Inputs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 603
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Placeholder for discussion about these facets of the style guide.
#### Talking points
- Select lists
- With and without "new item" input
- Text input
- Password inputs
- Confirmation (Y/N/abort)
- Args, command option and flag usage
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
Begin by reviewing the listed style-guide talking points: select lists, text and password inputs, confirmation prompts, and argument or flag usage. The issue does not name files or tests; first clarify the desired conventions and scope, then document the agreed guidance so each listed input case is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100