luckyframework / luckyframework/lucky_task
Creation of an "Args" object
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Following https://github.com/luckyframework/lucky_task/issues/23
We had some discussions about the method names that get generated on to the task. What if we moved all of these methods in to a new "Args" object. So instead of calling `name` from `--name` you'd call `args.name`. [Habitat](https://github.com/luckyframework/habitat) pretty much works this same way with settings. You would have `my_thing.settings.name`, or whatever the setting is.
This would also have the added benefit of being able to override the names for your own custom methods, or possibly add additional validation type functions.
Contributor guide
No contributing guide indexed for this repository
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 reading issue #23 and reviewing how task methods are currently generated. Compare the proposed Args-object approach with Habitat's settings pattern. Done would mean the design and affected generated methods are clearly defined, including how custom methods and additional validation functions would work.
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
- Needs clarification
- Newbie friendliness
- 25/100