mapbox / mapbox/mapbox-maps-android

Mak MapApplier public

Open
#2,664 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triaged feature :green_apple:
Dominant language
Kotlin
Stars
578
Forks
161
PR merge metrics
No merged PRs in 30d

Description

If we need to create our own component, we're blocked because MapApplier is marked as internal.
Why this blockage?
I'd like to use Mapbox Compose with navigation, and I need to implement my own component, but that's impossible given this blockage.
Otherwise, please make Mapbox Navigation a Compose component.

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 locating the MapApplier API and the Mapbox Compose/navigation integration referenced in the issue. Clarify whether the intended scope is exposing MapApplier or providing a Compose navigation component; done when one agreed use case is supported and its public API behavior is verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.