Cleanup blockers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
There should probably be some general cleanup of the codebase and directory structure. But be careful not to break outstanding PRs that should be merged eventually after some more work:
* https://github.com/mapbox/tippecanoe/pull/303 Nested attributes
* https://github.com/mapbox/tippecanoe/pull/468 Shapefile input
* https://github.com/mapbox/tippecanoe/pull/506 Data type cleanup
* https://github.com/mapbox/tippecanoe/pull/533 Use vtzero
* https://github.com/mapbox/tippecanoe/pull/514 Detect features within features
* https://github.com/mapbox/tippecanoe/pull/551 Mergeable features
* https://github.com/mapbox/tippecanoe/pull/539 JSON form for command-line options
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 reviewing the codebase and directory structure alongside the listed pull requests, especially Nested attributes, Shapefile input, Data type cleanup, and Use vtzero. Identify cleanup candidates only after understanding those outstanding changes, and ensure the resulting organization does not break work intended for eventual merging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100