Currently, if you add .location to available inputs, when you're about to share a location you get options for both static location and live location.
Ideally, apps using the library should have the option to use static location without displaying the live location button.
For example, the .location available input could be split into .staticLocation and .liveLocation, and these lines could become conditioned on the availability of .liveLocation:
|
pickerActionButton(localization.shareLiveLocationText, filled: false) { |
|
showLiveDurationDialog = true |
|
} |
Feel free to ignore / close this issue if you wish, as users can fork the library and comment those lines if they don't want to use live location.
Currently, if you add
.locationto available inputs, when you're about to share a location you get options for both static location and live location.Ideally, apps using the library should have the option to use static location without displaying the live location button.
For example, the
.locationavailable input could be split into.staticLocationand.liveLocation, and these lines could become conditioned on the availability of.liveLocation:Chat/Sources/ExyteChat/Views/Location/LocationPickerView.swift
Lines 63 to 65 in 259188e
Feel free to ignore / close this issue if you wish, as users can fork the library and comment those lines if they don't want to use live location.