You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed, with the current implementation, all the placemark methods internally create an instance of CLGeocoder.
I would like to ask, what is your opinion on exposing them publicly, and putting a Reactive extension on CLGeocoder?
I don't mind doing it myself, so long as the idea gets approved.
Benefits would be that you can do reverse geocoding on any CLLocation, not just the user's current location.
The text was updated successfully, but these errors were encountered:
I noticed, with the current implementation, all the
placemark
methods internally create an instance ofCLGeocoder
.I would like to ask, what is your opinion on exposing them publicly, and putting a
Reactive
extension onCLGeocoder
?I don't mind doing it myself, so long as the idea gets approved.
Benefits would be that you can do reverse geocoding on any CLLocation, not just the user's current location.
The text was updated successfully, but these errors were encountered: