Skip to content

Releases: iZettle/Flow

Flow 1.8.4

30 Mar 12:55
7d58628
Compare
Choose a tag to compare
  • Fix compilation errors in Xcode 11.4
  • Use Swift.Result instead of custom result implementation
  • Update sample to match readme.

Flow 1.8.3

29 Oct 13:18
cae0957
Compare
Choose a tag to compare
  • Fix race conditions for iOS 13 for Signal and cleanup CallbackState
  • Add new combiner driven(by:) that makes a ReadSignal emit its latest readable values when the given "driver" signal fires events. The combined signal will derive its signal kind from the driver, but without write access.

Flow 1.8.2

24 Jul 14:57
3f93992
Compare
Choose a tag to compare
  • Fix the traitCollectionWithFallback behaviour on iOS 13 to return the view's predicted traits and prior iOS 13 to respect the key window's traits before falling back to the main screen traits.

Flow 1.8.1

04 Jul 14:49
51ba63b
Compare
Choose a tag to compare
  • Added signal transformations contains(where:) and allSatisfy(where:) as wrappers for boolean reduce() transforms.
  • Changed reduce() implementation to consider initial values when performed on readable signals.

Flow 1.8.0

29 Apr 13:27
e7305c0
Compare
Choose a tag to compare
  • Added deallocSignal(for:) and NSObject.deallocSignal for listen on deallocation of objects.
  • Added signal transformation with(weak:) as a convenience helper for breaking retain cycles.

Flow 1.7.0

01 Apr 09:39
6a8ec12
Compare
Choose a tag to compare
  • Migrate to swift 5.

Flow 1.6.0

21 Mar 13:00
50df2ac
Compare
Choose a tag to compare
  • Addition: Make Callbacker conform to SignalProvider.

Flow 1.5.2

04 Mar 11:17
6064b50
Compare
Choose a tag to compare
  • Bugfix: Make sure shared() updates its last value before calling out to get correct results in case of recursion.

Flow 1.5.1

13 Feb 12:10
eebfc95
Compare
Choose a tag to compare
  • Updates combineLatest to no longer allow mixing of plain and readable signals as for the returned signal to guarantee to be readable all provided signals must as be readable as well. This is technically a breaking of the API, but as the existing implementation is broken and might result in run-time crashes, this change can be considered as a bug-fix.

Flow 1.5.0

14 Dec 15:30
d264b76
Compare
Choose a tag to compare
  • Added new Future and Signal delay alternatives that accepts a closure that returns the delay based on the value allow variable delays.
  • Fixed a couple of memory leaks.