maplibre / maplibre/maplibre-react-native
Support for Feature State API
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 661
- Forks
- 124
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 30
Description
MapLibre Native is currently implementing the `feature-state` API ([maplibre-native #1698](https://github.com/maplibre/maplibre-native/issues/1698)), which allows for dynamic styling of individual features without re-parsing the entire data source. This is useful for selection states, etc.
I suggest implementing `setFeatureState` and `getFeatureState` on the MapView/Source refs, similar to the implementation found in [rnmapbox #3741
](https://github.com/rnmapbox/maps/pull/3741)
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 at the MapView and Source refs and compare the requested API with the MapLibre Native feature-state work in maplibre-native #1698. Review rnmapbox pull request #3741 for the analogous implementation. Done means setFeatureState and getFeatureState are exposed and work for dynamic feature styling on the supported platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- api, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100