Changelog History
Page 3
-
v8.4.0 Changes
December 17, 2020Feat
- hit _geoloc field improvement (#704) (b13998c)
-
v8.3.0 Changes
November 23, 2020 -
v8.2.0 Changes
November 03, 2020Feat
- set tagged/untagged ranges calculation lazy in TaggedString (#689) (59daf69)
-
v8.1.3 Changes
October 27, 2020 -
v8.1.2-beta.1
September 30, 2020 -
v8.1.1 Changes
September 17, 2020- π Fix infinite hosts rotation within retry strategy (#664)
- β Add explicit percent encoding for plus sign in the browse cursor, lack of which causes browse API call error
-
v8.1.0 Changes
August 04, 2020π This minor release adds a possibility to update multiple fields of the record using
partiaUpdate
method with new dictionary syntax:index.partialUpdateObject(withID: "userAccountID", with: ["name": "John Doe", "postsCount": 2000, "followers": .add(value: "nightStranger51", unique: false), "followersCount": .increment(value: 20), "likes": .incrementSet(value: 15)])
-
v8.0.1 Changes
July 28, 2020- β Add Xcode 12 compatibility
- β Add
Client
typealias forSearchClient
to simplify the transition from v7
-
v8.0.0 Changes
July 20, 2020Meet brand new Swift API Client v8!
Universal
Itβs a pure stand-alone Swift client so it is not tighten to any platform.
In comparison with the previous version, it provides many new methods and from now can be used as a full-fledged client including server side applications.Provides good Results
Each API call result is now represented by built-in Swift
Result
type which facilitates processing of the results returned by the API method and to dispatch them to other parts of your application.Codable all the things
The interaction with API client is drastically simplified thanks to usage of built-in
Encodable
/Decodable
protocols.
Integration ofCodable
models existing in your project had never been easier.Advanced Keypaths usage
π Build API Client structures using the power of Swift keypaths
π Rich code documentation
Each method is documented with detailed description of each parameter
Verbosity
π The new client is verbose so it let know whatβs going on while you are using the client. You won't miss if something went wrong. Itβs up to you to define which level of logs you might want to see in your console. You can change it using
AlgoliaSearchClient.Logger.minSeverityLevel
value. -
v8.0.0-beta.9
June 18, 2020