mapbox / mapbox/mapbox-maps-flutter
Minor nit: `MAPBOX_DOWNLOADS_TOKEN` vs `SDK_REGISTRY_TOKEN`
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 380
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
The mapbox-maps-flutter flutter library seems to use SDK_REGISTRY_TOKEN as the property that holds the appropriate API key. However, the Android Installation guide uses MAPBOX_DOWNLOADS_TOKEN.
This now means I have a .gradle/gradle.properties file with the same token twice. It's a minor nit, and a minor inconvenience.
Can we change mapbox-maps-flutter to accept either SDK_REGISTRY_TOKEN or MAPBOX_DOWNLOADS_TOKEN? Happy to send a PR.
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 comparing the mapbox-maps-flutter credential setup with the Android Installation guide's Configure credentials section. Trace where SDK_REGISTRY_TOKEN is read and determine whether MAPBOX_DOWNLOADS_TOKEN can be accepted there. Done means either property supplies the required token, avoiding duplicate entries in .gradle/gradle.properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100