mapbox / mapbox/vtfx

First tag backlog

Open
#27 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Description

- [x] Merge GC branch
- [x] Unit test each vtfx using layer objects (rather than a "real" PBF layer)
- [x] Benchmark each vtfx
- [ ] Open upstream PRs for protocol-buffers js
- [x] Vet parameters for each vtfx, add tests to make sure no one redefines parameters willy-nilly
- [ ] Test performance/stability in context of mapbox-studio

cc @camilleanne @ian29

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.

Research direction

Start by reviewing the two unchecked checklist items: opening upstream pull requests for protocol-buffers js and testing performance and stability in the context of mapbox-studio. Use the completed unit-test, benchmark, and parameter-vetting work as context. Done means both remaining tasks have been addressed and their outcomes are recorded in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.