Port CLI over to using module functionality

Open
#45 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
cli

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.

Description

loe 2 sdk-cli

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

Dominant language
Python
Stars
141
Forks
27
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/tilesets-cli

All issues in mapbox/tilesets-cli

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.