luckyframework / luckyframework/lucky_cli
IO managment
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 92
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
I think we should include a standard IO management for all the CLI commands. This might be able to be pulled into the core Lucky lib. I have built a few CLIs in Crystal now and I have been doing IO managment and think I have found a suitable pattern since there is no default CLI framework in Crystal.
I think we should have three methods accessible to the CLI commands `input_io`, `data_io`, and `human_io`. This makes it very easy to check `input_tty?` and only output the IO you actually need. This more conforms to UNIX style programs and lucky easier to use with other linux tools.
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
No files or tests are named. Start by locating the CLI command entry points and existing IO handling, then assess how input_io, data_io, and human_io could be exposed through the core Lucky library. Done means CLI commands can use these streams, check input_tty?, and behave correctly in Unix-style pipelines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100