No good way to create a 'Parsed' object
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- cli
Research direction
Start with the --run=:: entry point and inspect how the Parsed object is passed to foo. Compare direct construction with the proposed option-extraction and future Cli designs. Done means the project has a decided, documented API for invoking foo directly, with the relevant behavior covered.
Written by the indexing model from the issue text.
Description
It's currently common to call a method with the Parsed object:
--run=:: foo it
foo parsed/cli.Parsed:
...
If I wanted to call the foo function directly, then I would need to create a Parsed object myself. That's currently not really possible.
We should either make this possible, or discourage passing the Parsed object around.
For example, we could encourage to always extract the options in the lambda:
--run=:: foo it["option1"] it["option2"] ...
That could get messy, and would go against future API plans, where we would like to give a Cli object that has ui, config, and cache (in addition to parsed). That said, maybe parsed shouldn't be part of that object.
- Dominant language
- Toit
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from toitlang/pkg-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Add support for multi rests followed by a non-multiMay be free again @floitsch claimed this 1228 days ago, and no pull request is open. Open
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in toitlang/pkg-cli
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
spectreconsole/spectre.console#2221 · 1 comment ·
Maintainers usually reply within 1 day
-
follow ups for #38Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tenstorrent/tt-cli#52 ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
PedestrianDynamics/pyFDS-Evac#475 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days