Releases: stadiamaps/swiftui-autocomplete-search
4.0.0
What's Changed
- No longer forces an
Identifiableconformance (removes a possible source of future breakage) by @bolsinga in #1 - Adds a library version of the autocomplete function and internal logic for easier use by library consumers (if you're reading this, the chances you actually need this are relatively slim, but this does help simplify the code in some apps; otherwise you should probably use the stadiamaps package directly for "headless" geocoding) by @bolsinga in #2
- Upgrade to the search API v2 by @ianthetechie in #3
Breaking changes
This release changes the custom result view builder interface. A relativeTo location parameter is no longer needed, as the v2 API always calculates the distance to search results. The code in the app layer is now redundant, so we deleted it.
New Contributors
Full Changelog: 3.0.1...4.0.0
3.0.1
This is a bug fix release which corrects the a bug in the search result distance display.
Full Changelog: 3.0.0...3.0.1
3.0.0
This release brings support for the faster, better, and cheaper v2 autocomplete API!
The library will feel more or less the same, but the response models have changed a bit to include more data and better structure. For an overview of the structural changes we've made in the V2 API, refer to the migration guide.
Full Changelog: 2.0.2...3.0.0
2.0.2
Adds logging of failed requests and resolution tips using the standard OSLog framework.
Full Changelog: 2.0.1...2.0.2
2.0.1
This fixes a bug due to some code not being committed in the 2.0.0 release (see the release notes for migration instructions).
Full Changelog: 2.0.0...2.0.1
2.0.0
This release upgrades the stadiamaps-api-swift dependency to version 5. This release adds support for Foursquare OS Places as a searchable data source. Millions of new restaurants, shops, and other businesses are now at your fingertips. (Currently opt-in beta; see the release announcement here: https://stadiamaps.com/news/geocoding-foursquare-beta/. Foursquare results will be enabled by default in the near future.)
This is a breaking change which renames some types that had a Pelias prefix to a Geocoding prefix.
Full Changelog: 1.4.0...2.0.0
1.4.0
This release includes a number of visual improvements, particularly for use cases where the view is designed to be an overlay as part of a larger UI. It also adds a configurable minimum query length.
1.3.0
This release adds support for filtering by layer. For example:
AutocompleteSearch(apiKey: "YOUR-API-KEY", limitLayers: [.coarse]) { selection in
print("Selected: \(selection)")
}Full Changelog: 1.2.0...1.3.0
1.2.0
This release polishes up the result display with more local context and better iconography.
1.1.1
This release improves the quality and completeness of the generated documentation.
Full Changelog: 1.1.0...1.1.1