wildcard in tileset delete
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the tilesets delete command in mapbox_tilesets/scripts/cli.py, especially the delete function near line 220, and reproduce the wildcard example from the issue. Trace how the command validates and sends the tileset ID; done means a wildcard such as projected can identify matching tilesets and handle deletion safely.
Written by the indexing model from the issue text.
Description
I've got a few hundred tilesets to manage, is there a potential for wildcard of tileset ids?
For example, delete any tilesets with "projected" in their id name:
(Zooniverse) MacBook-Pro:Zooniverse ben$ tilesets delete *projected*
To confirm tileset deletion please enter the full tileset id "*projected*": *projected*
Traceback (most recent call last):
File "/Users/ben/miniconda3/envs/Zooniverse/bin/tilesets", line 8, in <module>
sys.exit(cli())
File "/Users/ben/miniconda3/envs/Zooniverse/lib/python3.7/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/Users/ben/miniconda3/envs/Zooniverse/lib/python3.7/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/Users/ben/miniconda3/envs/Zooniverse/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/Users/ben/miniconda3/envs/Zooniverse/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/Users/ben/miniconda3/envs/Zooniverse/lib/python3.7/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/Users/ben/miniconda3/envs/Zooniverse/lib/python3.7/site-packages/mapbox_tilesets/scripts/cli.py", line 220, in delete
raise errors.TilesetsError(r.text)
mapbox_tilesets.errors.TilesetsError: {"message":"Not Found"}
- Dominant language
- Python
- Stars
- 141
- Forks
- 27
- 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 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
-
dead_air_detection fails on m4a/AAC audio ("Could not decode audio: Format not recognised") for uploads, base64 and own-bucket recordingsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
future-agi/future-agi#3317 ·
Maintainers usually reply within 1 day
-
Failed agent type collection replaces a complete snapshot with partial dataPossibly taken @SahilKumar75 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
task
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#133181 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bmad-code-org/BMAD-METHOD#3041 ·
Maintainers usually reply within 1 day