Support user input
Open
design decision required
- Dominant language
- Rust
- Stars
- 38
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Yes, I know, this library's code name is "output".
Still, we need to support reading user input to support prompts and such, without messing up what they are typing.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the library's output and logging entry points, then determine how prompts should read input without interfering with typed text. Done means user input is supported for prompts while existing output behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100