Releases: contentful/contentful.swift
Releases · contentful/contentful.swift
1.0.0-beta5
Added
- Instance method for mutating a query by appending a
LinkQuery
Fixed
- When generating a url from the helper methods that append
ImageOptions
, the 'https' scheme will always be applied. - The
Location
type is now an Objective-C that conforms to NSCoding class so that it may be stored in CoreData as an attribute on anNSManagedObject
1.0.0-beta4
Fixed
- Accessibility identifiers for the
width
andheight
properties of theImageInfo
for anAsset
are now public so they can be used. Thanks to @ErikLuimes for the pull request: #157 - The
Location
type is now an Objective-C class so that it may be stored in CoreData as an attribute on anNSManagedObject
1.0.0-beta3
Fixed
- Issue where
true
would be decoded toInt
with value1
when decoding JSON to[String: Any]
. The SDK now attempts to decodeBool
beforeInt
to prevent this error.
1.0.0-beta2
Fixed
- Deprecation warnings that appeared starting with Xcode9.1
- Incorrect assertion that asserted that all link were resolved since it is possible for unresolvable links to retured from CDA
- If an entry was of a content type not known to the
Client
, the SDK would enter an infinite loop.
1.0.0-beta1
Added
ResourceQueryable
protocol to enable safer queries via theQueryOn
query type.SyncSpace.SyncableType
enum for specifying which Contentful types should be synced.- A description property to
ContentType
- A
ContentTypeQuery
for syncing content types. ArrayResponseError
type as a member of all array responses to inform you when your links are not resolvable because the target resources are unpubished.
Improved
- All Error types now have better debug descriptions so that the most relevant info is given to you while debugging.
Fixed
- Multiple link resolution callbacks can now be stored for one link in case multiple entries are linking to the same resource.
Changed
- BREAKING: The helper methods for resolving links on the fields JSON container no longer requires passing in the current locale.
- BREAKING: The parameter names have been made consistent accross all fetch method names. The parameter signatures for all fetch methods are now:
(matching:then:)
. - BREAKING: All query initializers have been changed to static methods so that the syntax exactly matches the syntax of the instance methods.
- BREAKING: Various methods for creating and mutating queries no longer
throw
errors and so the need to call them in ado
catch
block has been obviated. - BREAKING:
QueryOperation
is now calledQuery.Operation
.
Removed
- BREAKING: All fetch methods that previously took dictionary arguments have been removed. Use fetch methods that take query types instead.
- BREAKING: Now unnecessary
QueryError
s.
0.11.0
Changed
- BREAKING:
EntryModellable
is now calledEntryDecodable
and extendsDecodable
from the Swift 4 Foundation standard library. There are convenience methods for deserializing fields in the "fields" container for an entry. - BREAKING: The
MappedContent
type no longer exists. If requesting heterogeneous collections (by hitting "/entries" with no query paramters for intance), you will get aResult<MixedMappedArrayResponse>
and it is up to you to filter the array by the contained types.
Fixed
0.10.2
0.10.1
0.10.0 — Swift 4
Changed
- BREAKING: The project is now compiled using Swift 4 and therefore must be developed against with Xcode 9. Backwards compatibility with Swift 3 is not possible as the SDK now uses Swift 4 features like JSON decoding via the
Decodable
protocol in Foundation. - BREAKING:
CLLocationCoordinate2D
has been replaced withLocation
type native to the SDK so that linking with CoreLocation is no longer necessary. If you have location enabled queries, you'll need to migrate your code. Resource
is now a protocol and is no longer the base class forAsset
andEntry
.LocalizableResource
is the new base class.- ObjectMapper has been pruned and is no longer a dependency of the SDK. If managing your dependencies with Carthage, make sure to manually remove ObjectMapper if you aren't using it yourself.
0.9.3
Fixed
- Ensured all functions and instance members had an explicit protection level set.
Added
- Xcode 8 and 9 are now tested on Travis CI for iOS, macOS, and tvOS in a matrix build. You can now rest easy knowing that if you are developing for one of these platforms, the SDK will work for you!
- The Swift playground has been migrated from it's former home to live here, with the main SDK. Instructions have been added to the README.
DataDelegate
protocol to receive callbacks from SDK which contain rawData
from fetches to the API.