Christian Tietze

Could we maybe make Middlewares easier for users to pick up? I'm Stockholm-syndrome-ified and know how to use Middlewares nowadays, but the language has changed since ReSwift 6, so maybe...

I opened a discussion for a breaking API change to make the `Store` non-open. (Mostly because I don't see why we have that, to be honest :)) -- [Please chime...

I really like the overall changes! That reads much nicer than the old block stuff. In general, I think the side effect of activating the subscription in the Store.subscription() factory...

@mjarvis Aha! So the store becomes a hub of subscriptions that each manages its own subscribers, right? Sounds clever, and reasonable. The concepts work, kind of: a subscription has many...

I experimented with the changes and tried to fix some broken tests, then I split the Subscription type into subtypes to see if that makes getting a handle on things...

@mjarvis here it is so far: https://github.com/ReSwift/ReSwift/tree/DivineDominion/invert-transform-types

Odd that recent builds with Swift 5.4 work fine. The watchOS target there breaks because of the XCTest module. The build command is ``` env DEVELOPER_DIR="/Applications/Xcode_12.2.app" xcrun xcodebuild -IDEClonedSourcePackagesDirPathOverride="$PWD/.dependencies" -derivedDataPath...

`master` looks quite ok now, except ## watchOS on Swift 5.1/5.2/5.3 The build process tries to use XCTest, which isn't available. Since tests aren't run by the Swift package index...

I'd like to know more about why you folks need redux-saga and similar any why vanilla ReSwift won't cut it.

Beats me to fix the `Package.swift`. I think one would have to re-organize the code folder for multi-platform manifests, or change the project to have 1 target for all platforms....