- Notifications
You must be signed in to change notification settings - Fork2
Our fork of ReactiveSwift that fixes SPM compatibility by removing testing libraries.
License
Moya/ReactiveSwift
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation

Streams of values over time. Tailored for Swift.

🎉Getting Started 🚄Release Roadmap
ReactiveSwift offers composable, declarative and flexible primitives that are built around the grand concept ofstreams of values over time.
These primitives can be used to uniformly represent common Cocoa and generic programming patterns that are fundamentally an act of observation, e.g. delegate pattern, callback closures, notifications, control actions, responder chain events,futures/promises andkey-value observing (KVO).
Because all of these different mechanisms can be represented in thesame way,it’s easy to declaratively compose them together, with less spaghetticode and state to bridge the gap.
An overview of the semantics and example use cases of the ReactiveSwift primitives, including
Signal,SignalProducer,PropertyandAction.An overview of the operators provided to compose and transform streams of values.
Building on top of ReactiveSwift,ReactiveCocoa extends Cocoa platform frameworks with reactive bindings and extensions.
How does ReactiveSwift relate to RxSwift?
An overview of how ReactiveSwift differs from RxSwift for Swift idiomaticity.
Interactive Form UI
ReactiveSwift includes aUI Examples playground, which demonstrates:
- how to build an interactive form UI with bindings, properties and
Actions, with a live view in action. - how to use reactive primitives to implement the Model-View-ViewModel architectural pattern, with the View Model being the source of truth for the View.
- how to build an interactive form UI with bindings, properties and
Bindings and reactive extensions for Cocoa and Cocoa Touch frameworks are offered separately as ReactiveCocoa.
Contracts of the ReactiveSwift primitives, Best Practices with ReactiveSwift, and Guidelines on implementing custom operators.
ReactiveSwift supports macOS 10.9+, iOS 8.0+, watchOS 2.0+, tvOS 9.0+ and Linux.
If you useCarthage to manage your dependencies, simply addReactiveSwift to yourCartfile:
github "ReactiveCocoa/ReactiveSwift" ~> 5.0If you use Carthage to build your dependencies, make sure you have addedReactiveSwift.framework to the "Linked Frameworks and Libraries" section of your target, and have included them in your Carthage framework copying build phase.
If you useCocoaPods to manage your dependencies, simply addReactiveSwift to yourPodfile:
pod 'ReactiveSwift', '~> 5.0'If you use Swift Package Manager, simply add ReactiveSwift as a dependencyof your package inPackage.swift:
.package(url: "https://github.com/ReactiveCocoa/ReactiveSwift.git", from: "5.0.0")- Add the ReactiveSwift repository as asubmodule of yourapplication’s repository.
- Run
git submodule update --init --recursivefrom within the ReactiveCocoa folder. - Drag and drop
ReactiveSwift.xcodeprojinto your application’s Xcodeproject or workspace. - On the “General” tab of your application target’s settings, add
ReactiveSwift.frameworkto the “Embedded Binaries” section. - If your application target does not contain Swift code at all, you should alsoset the
EMBEDDED_CONTENT_CONTAINS_SWIFTbuild setting to “Yes”.
We also provide a great Playground, so you can get used to ReactiveCocoa's operators. In order to start using it:
- Clone the ReactiveSwift repository.
- Retrieve the project dependencies using one of the following terminal commands from the ReactiveSwift project root directory:
git submodule update --init --recursiveOR, if you haveCarthage installedcarthage checkout
- Open
ReactiveSwift.xcworkspace - Build
ReactiveSwift-macOSscheme - Finally open the
ReactiveSwift.playground - Choose
View > Show Debug Area
If you need any help, please visit ourGitHub issues orStack Overflow. Feel free to file an issue if you do not manage to find any solution from the archives.
ReactiveSwift is expected to declare library ABI stability when Swift rolls out resilence support. Until then, ReactiveSwift would incrementally adopt new language features that help move towards to goal. The ETA is Swift 5.
About
Our fork of ReactiveSwift that fixes SPM compatibility by removing testing libraries.
Resources
License
Contributing
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Languages
- Swift99.2%
- Other0.8%