-
Notifications
You must be signed in to change notification settings - Fork 35
Geocoding example #17
Comments
How should external dependencies be presented to the user? |
It should be sufficient to link to the Mapbox*.swift projects’ READMEs. If those READMEs are lacking, please expand on anything that I’ve glossed over. I don’t think it’ll be so bad: once the user has installed our iOS SDK, these libraries can be installed using much the same workflows. (Granted, it’d be more of a leap for Fabric users – no jiggling briefcase animations this time.) More broadly, we can consider expanding the /ios-sdk front page with dedicated sections for the Mapbox*.swift libraries, like what we’ve got on /android-sdk. But that suggests a rename from /ios-sdk to /ios, which is overkill for now. |
/ios-sdk now covers all the SDKs. This project, meanwhile, already depends on the navigation SDK and thus MapboxDirections.swift, so a dependency on MapboxGeocoder.swift doesn’t sound so bad. |
It doesn't anymore 😁 and nav examples were moved to their own repo in #324. Because of this, I'm inclined to close this, and keeping examples in |
There should be an example in which the user can long-press the map to drop a pin and see its address, geocoded using the Geocoding API via MapboxGeocoder.swift.
/ref #6
/cc @friedbunny @tmcw
The text was updated successfully, but these errors were encountered: