Releases: wisemen-digital/AppwiseCore
Releases · wisemen-digital/AppwiseCore
2.1.0
Deprecations
- Core: deprecate our
Cancelled
error type in favour of Swift's built-inCancellationError
type. - CoreData: due to incorrectness, we're deprecating
responseInsert
(this is notresponseInsert
, see below).
Improvements
- Behaviours: add keyboard avoiding behaviour (using the system provided layout guide).
- CoreData: make
SingleObjectRepository
compatible withOptionalIdentifiable
. - CoreData: lower the requirement of repositories to
NSFetchRequestResult
where possible. - CoreData: repository
refresh
now asserts by default, to better warn about missing implementations. - Core: add
requestVoid
method to network client. - Core: default error parser now ignores
.explicitlyCancelled
(for cancelled requests). - Core: result "cancellation" now uses Swift's built-in
CancellationError
type if available. - Core: add privacy manifest file
- XcodeGen: added a template for shared frameworks.
Bug Fixes
- Fastlane: ensure translations export can handle "empty" targets.
- Scripts: fix Xcode warnings for build steps without input/output files.
- Bump dependencies (Sentry to 8).
- CoreData: ensure
requestInsert
imports objects on the context's thread. - Sourcery: fix code generation for
Self.ID
properties. - SwiftLint: fix warnings from using deprecated rules (because we use
all
).
Internal
- Bump copyright.
2.0.3
2.0.2
1.4.6
2.0.1
1.4.5
2.0.0
Breaking
- Updated to Alamofire 5.0, causing some breaking changes for Network clients and related types.
- Switched to Swift's built-in
Result
type, which requires anError
generic parameter. - It is recommended to use the migration script when possible, it will convert most common breaking changes.
1.4.4
1.4.3
Improvements
- Bump SentrySDK version from 6 to 7. Make sure you configure a trace sample rate! This should NOT be a breaking change, but if needed, check their migration docs.
1.4.2
Internal
- Lint & format code, and add commit hooks to trigger these.
- Bump SentrySDK version from 5 to 6. This should NOT be a breaking change, but if needed, check their migration docs.