Post layer statistics when a job succeeds
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the tilesets status <tilesetID> command and trace how a successful response is handled. Determine how the previous and newly published tileset versions and their layer statistics can be obtained through the existing CLI/API flow. Done means a successful status response also reports the requested comparison without changing other status behavior.
Written by the indexing model from the issue text.
Description
When tilesets status <tilesetID> returns {"status": "success"} It would be great if it also output layer statistics between the previous version of the tileset and the newly published version 📊
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
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.
More from mapbox/tilesets-cli
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
mapbox/tilesets-cli#217 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
mapbox/tilesets-cli#216 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mapbox/tilesets-cli#193 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
mapbox/tilesets-cli#190 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mapbox/tilesets-cli#171 · 1 reaction ·
All issues in mapbox/tilesets-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100