luckyframework / luckyframework/lucky
If using `lucky watch` directly, tell users to use `lucky dev`
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
https://gitter.im/luckyframework/Lobby?at=5d408aa5c356af25e0580790
It is unclear what the best option is here. Maybe we print a warning if using `lucky watch` without a specific flag? Maybe an ENV var is set?
The ENV var might be nice because if you prefer to use `lucky watch` in all your projects you can export it in your shell. `SILENCE_LUCKY_WATCH_WARNING=true` or something likethat
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 Crystal implementations of the `lucky watch` and `lucky dev` commands. Review the linked Gitter discussion and existing command behavior before deciding whether a warning or an environment-variable opt-out is appropriate. Done means the intended guidance is implemented and its behavior is covered by the relevant command tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100