luckyframework / luckyframework/lucky
Built-in Tasks should use the native CLI args
Open
Nobody has claimed this yet.
clarify api
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
A lot of the built-in tasks use ARGV and should just take advantage of our native CLI Args.
These are currently done:
- - exec task
- - watch task
These will require some thought on how to better do error handling:
- - security_key task
- - page
- - model
- - component
- - action
- - resource
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 built-in task implementations and the native CLI Args entry point, then compare them with the completed exec and watch tasks. Migrate security_key, page, model, component, action, and resource to native CLI Args, with the error-handling behavior resolved for each task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100