Port CLI over to using module functionality
Open
Nobody has claimed this yet.
loe 2
sdk-cli
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Relates to #42
Our CLI should use the same module functions that python applications will use. Once we've completed recreating functionality in a module, we should port over the CLI to exclusively use this module.
This will serve to both lower our footprint, as well as be a clear example of module implementation.
cc @Gerdie
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 reading issue #42 and tracing the current CLI entry points alongside the module functionality it is meant to reuse. Identify which CLI paths still bypass the module; done means the CLI exclusively uses the recreated module functions and continues to provide the same command behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100