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
This library currently has a Core Location dependency as a “location” parameter seems commonly useful enough to warrant inclusion. I can understand developers not wanting to pull this in so am interested in suggestions on how to best structure this. Perhaps a XExtensionItem+Location subspec that augments the core library with these capabilities?
The text was updated successfully, but these errors were encountered:
Considering removing location support altogether for now, considering it's likely not something would encourage, even though I think there are valid use cases that aren't just sending the user's current location from an app that has permissions to an extension that doesn’t (e.g. sharing a Foursquare check-in to an extension like Day One's).
Considering it's likely not something would encourage
Yeah, thinking about it a bit, that’s probably true. Like you said, you could be sharing the location of a historic site, or a checkin, and not just where you are, but probably so few people would use that, that it isn’t worth being in the 1.0 anyway.
This library currently has a Core Location dependency as a “location” parameter seems commonly useful enough to warrant inclusion. I can understand developers not wanting to pull this in so am interested in suggestions on how to best structure this. Perhaps a
XExtensionItem+Location
subspec that augments the core library with these capabilities?The text was updated successfully, but these errors were encountered: