Releases: ReSwift/ReSwift
Releases · ReSwift/ReSwift
2.0.0
Released: 06/30/2016
Breaking API Changes:
- Significant Improvements to Serialization Code for
StandardAction
(relevant for recording tools) - @okla
Other:
- Swift 2.3 Updates - @agentk
- Documentation Updates & Fixes - @okla, @gregpardo, @tomj, @askielboe, @mitsuse, @esttorhe, @RyanCCollins, @thomaspaulmann, @jlampa
1.0.0
The first major release of ReSwift 🎉 From here on forward we will be using semantic versioning.
API Changes:
- Remove callback arguments on synchronous dispatch methods - @Ben-G
Other:
0.2.5
Released: 02/20/2015
API Changes:
- Subscribers can now sub-select a state when they subscribe to the store (#61) - @Ben-G
- Rename initially dispatched Action to
ReSwiftInit
- @vfn
Fixes:
- Fix retain cycle caused by middleware (issue: #66) - @Ben-G
- Store now holds weak references to subscribers to avoid unexpected memory managegement behavior (issue: #62) - @vfn
- Documentation Fixes - @victorpimentel, @vfn, @juggernate, @raheelahmad
Other:
- We now have a hosted documentation for ReSwift - @agentk
- Refactored subscribers into a explicit
Subscription
typealias - @DivineDominion - Refactored
dispatch
forAsyncActionCreator
to avoid duplicate code - @sendyhalim
0.2.4
API Changes:
- Pass typed store reference into
ActionCreator
.ActionCreator
can now accessStore
s state without the need for typecasts - @Ben-G Store
can now be initialized with an empty state, allowing reducers to hydrate the store - @Ben-G
Bugfixes
- Break retain cycle when using middelware - @sendyhalim
Other:
- Update Documentation to reflect renaming to ReSwift - @agentk
- Documentation fixes - @orta and @sendyhalim
- Refactoring - @dcvz and @sendyhalim
0.2.3
0.2.2
v0.2.1
v0.2
This release comes with the following major changes:
- Middleware Support
- Typed Actions are now used by default instead of serializable Actions
- Much API renaming
Details:
This Release Provides a Middleware API for Swift Flow. Further the library now uses typed actions by default. It is no longer required to provide actions that can be serialized. If you want to use Swift Flow Recorder, you can opt into serialization of actions.