4.2.1

Improved

• All reference documentation has been improved.

4.2.0: Logging

Added

• A ContentfulLogger singleton which will log messages to the console. ContentfulLogger can be configured with a CustomLogger in order to use any third-party logging frameworks of your choice.

4.1.3

Changed

• 4.1.1, 4.1.2, and 4.1.3 are all hotfix releases that fixed small corruptions in the Xcode project configuration. 4.1.3 specifically sets the deployment version on the macOS target, even though the correct deployment version was set on the macOS framework target.

4.1.2

The iOS deployment target was accidentally bumped when updating the SDK from version 4.0.0 to 4.1.0 and that caused an unexpected "breaking" change. This release reverts that mistake and also fixed a corrupted tvOS target (still a mystery how it was corrupted).

4.1.1 — Carthage only release

Release to fix issue when building projects that have spaces in the name: see #233

Contentful.framework.zip

4.1.0

Added

• The RichTextDocument type which can be used in EntryDecodable instances as a field type corresponding to rich text fields in Contentful.

Removed

• Support for iOS 8.

4.0.1

Merge pull request #236 from contentful/hotfix/swift-4.2-build

Run CI on Xcode 10

4.0.0

Changed

• BREAKING: Interstellar has been removed as a dependency of the SDK and the SDK now has its own Result type. If you were relying on fetch methods that returned an Observable, you will need to update your code.
• BREAKING: The syntax for many of the fetch methods on Client have changed. Refer to the v4 migration guide.
• BREAKING: EntryQueryable has been renamed FieldKeysQueryable, the required associated type Fields has been renamed FieldKeys to accurately reflect the type's real usage.
• BREAKING: MixedMappedArrayResponse has been renamed MixedArrayResponse.

Added

• Base fetch methods for fetching data, or fetching data and deserializing any type conforming to Swift.Decodable have been exposed so that SDK usage is more flexible for various development strategies.
• Endpoint enum and EndpointAccessible protocol for clarity on endpoints available through the APIs and which resource types are returned from said endpoints.
• ResourceQueryable protocol, which Asset, Entry, ContentType conform to; it enables querying and filtering on the API for conforming types.
• FlatResource protocol which can be used if you prefer to have all sys properties on the top level of your EntryDecodable. All Resource types have a default implementation of FlatResource so refactoring is opt-in.

Removed

• The DataDelegate protocol has been removed in favor of directly fetching raw Data on your own. If you want to store JSON to disk, simply fetch it and do what you like.
• The EntryModellable protocol is now gone. Just use EntryDecodable.

3.1.2

Fixed

A retain cycle due to the fact that the URLSession owned by Client was not invalidated on client deallocation. Thanks to @edwardmp for identifying the issue and submitting a fix in #226.

3.1.1

Fixed

• A critical bug that caused the fetchLocales(then:) method to not pass the correct error back to it's completion handler. This bug would, for example, incorrectly pass back an SDKError if internet connection dropped rather than passing back the proper NSErrror from Foundation.