Skip to content

Releases: ryanbaldwin/FireKit

v2.402.07

10 Nov 00:41
041996f

Choose a tag to compare

Summary

v2.40.07 & v2.402.07 fix a regression bug that I apparently slipped into a release a couple weeks back. Whoopsies.

Breaking Changes

None, son.

Gory Details

The realm.upsert(_ resources: [T]) -> [T] was crashing like a regular like a plane into the mountain. This is the original fix that was implemented over a month ago, and then promptly regressed because I'm a big dummy sometimes.

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

v2.401.07

10 Nov 15:03
041996f

Choose a tag to compare

Summary

v2.40.07, v2.401.07 & v2.402.07 fix a regression bug that I apparently slipped into a release a couple weeks back. Whoopsies.

Breaking Changes

None, son.

Gory Details

The realm.upsert(_ resources: [T]) -> [T] was crashing like a regular like a plane into the mountain. This is the original fix that was implemented over a month ago, and then promptly regressed because I'm a big dummy sometimes.

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

View build details and download artifacts on buddybuild:

v2.40.07

10 Nov 00:40
041996f

Choose a tag to compare

Summary

v2.40.07 & v2.402.07 fix a regression bug that I apparently slipped into a release a couple weeks back. Whoopsies.

Breaking Changes

None, son.

Gory Details

The realm.upsert(_ resources: [T]) -> [T] was crashing like a regular like a plane into the mountain. This is the original fix that was implemented over a month ago, and then promptly regressed because I'm a big dummy sometimes.

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

v2.402.06

09 Nov 01:56
9cf223c

Choose a tag to compare

Summary

v2.402.06 (and v2.40.06) addresses an issue with populate(from:) and property upset(...:) functions on Resources, wherein elements could be shared across resources. This is no longer the case.

Breaking Changes

None, son.

Gory Details

None

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

v2.40.06

09 Nov 01:54
9cf223c

Choose a tag to compare

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

v2.402.05

02 Nov 19:45
8b492ce

Choose a tag to compare

Summary

Same as v2.401.05, but for Swift 4.0.2 and Xcode 9.1.

Breaking Changes

None, son.

Gory Details

None

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

View build details and download artifacts on buddybuild:

v2.401.05

30 Oct 14:33
8b492ce

Choose a tag to compare

Summary

v2.401.05 is functionally identical to v2.401.04. The only difference between the 2 versions is v2.401.05 improves Carthage support by supporting --no-use-binaries flag, and enabling Carthage to properly build FireKit's dependencies. In essence, Carthage support now actually works as intended.

This addresses issue #17, which was both reported and fixed by the generous effort of @stupergenius. Buy him a beer next time you bump into him. Big thanks to @stupergenius!

Breaking Changes

None, son.

Gory Details

None

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

v2.401.04

25 Oct 19:09

Choose a tag to compare

Summary

This is simply a Xcode 9.0.1 bump for Carthage support. If you're using Carthage and Xcode 9.0.1, then you'll want to reference this version instead of v2.40.04. This is what happens when you couple a language version tightly to compiler version.

Breaking Changes

If you're on Xcode 9.0, then literally, probably, everything.

Gory Details

Nada

v2.40.04

22 Oct 22:25

Choose a tag to compare

Summary

Fixed a bug where populate(from:) would raise an error (and thus crash and make your life filled with sadness) if Elements were removed. For example, if you had a Patient instance with an associated meta, and you populate(from:) a Patient without a meta instance, then the world would end.

Breaking Changes

Here lies fixes, complete with unit tests.

Gory Details

Summary basically says it all.

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)

v2.40.03

11 Oct 18:25

Choose a tag to compare

Summary

For whatever reason, while running on an actual device, the following upsert function would crash.

@discardableResult public func upsert<R>(_ resources: [R]) -> [R] where R: Resource

I believe it was a result of a generic function calling a generic function, and there was type-loss in the static linking, though I am not sure. What I do know is that it is now fixed. Y'all should probably not use v2.40.02 if you make use of the above function.

Breaking Changes

None, in fact, these be fixing changes, yo.

Gory Details

Generic types and static linking and several layers mixed in with dynamically grabbing a type leads to a world of pain, as far as I can tell.

View build details and download artifacts on buddybuild:
FireKit (iOS, FireKit-iOS)