Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/JohnSundell/Flow
Operation Oriented Programming in Swift
https://github.com/JohnSundell/Flow
async operations swift
Last synced: 3 months ago
JSON representation
Operation Oriented Programming in Swift
- Host: GitHub
- URL: https://github.com/JohnSundell/Flow
- Owner: JohnSundell
- License: mit
- Created: 2015-11-05T22:17:17.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-01-26T23:07:36.000Z (almost 8 years ago)
- Last Synced: 2024-07-02T11:17:06.684Z (4 months ago)
- Topics: async, operations, swift
- Language: Swift
- Size: 51.8 KB
- Stars: 217
- Watchers: 9
- Forks: 6
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-ios - Flow - Operation Oriented Programming in Swift. (Concurrency / Linter)
- awesome-ios-star - Flow - Operation Oriented Programming in Swift. (Concurrency / Linter)
- fucking-awesome-ios - Flow - Operation Oriented Programming in Swift. (Concurrency / Linter)
- fucking-awesome-ios - Flow - Operation Oriented Programming in Swift. (Concurrency / Linter)
README
# Flow
[](https://github.com/Carthage/Carthage)
Flow is a lightweight Swift library for doing operation oriented programming. It enables you to easily define your own, atomic operations, and also contains an exensive library of ready-to-use operations that can be grouped, sequenced, queued and repeated.
## Operations
Using Flow is all about splitting your code up into multiple atomic pieces - called **operations**. Each operation defines a body of work, that can easily be reused throughout an app or library.
An operation can do anything, synchronously or asynchronously, and its scope is really up to you. The true power of operation oriented programming however, comes when you create groups, sequences and queues out of operations. Operations can potentially make code that is either asynchronous, or where work has to be done in several places, a lot simpler.
## How to use
- Create your own operations by conforming to `FlowOperation` in a custom object. All it needs to do it implement one method that performs it with a completion handler. It’s free to be initialized in whatever way you want, and can be either a `class` or a `struct`.
- Use any of the built-in operations, such as `FlowClosureOperation`, `FlowDelayOperation`, etc.
- Create sequences of operations (that get executed one by one) using `FlowOperationSequence`, groups (that get executed all at once) using `FlowOperationGroup`, or queues (that can be continuously filled with operations) using `FlowOperationQueue`.
## Example
Let’s say we’re building a game and we want to perform a series of animations where a `Player` attacks an `Enemy`, destroys it and then plays a victory animation. This could of course be accomplished with the use of completion handler closures:
```swift
player.moveTo(enemy.position) {
player.performAttack() {
enemy.destroy() {
player.playVictoryAnimation()
}
}
}
```
However, this quickly becomes hard to reason about and debug, especially if we start adding multiple animations that we want to sync. Let’s say we decide to implement a new **spin attack** in our game, that destroys multiple enemies, and we want all enemies to be destroyed before we play the victory animation. We’d have to do something like this:
```swift
player.moveTo(mainEnemy.position) {
player.performAttack() {
var enemiesDestroyed = 0
for enemy in enemies {
enemy.destroy({
enemiesDestroyed += 1
if enemiesDestroyed == enemies.count {
player.playVictoryAnimation()
}
})
}
}
}
```
It becomes clear that the more we add to our animation, the more error prone and hard to debug it becomes. Wouldn’t it be great if our animations (or any other sequence of tasks) could scale gracefully as we make them more and more complex?
Let’s implement the above using Flow instead. We’ll start by defining all tasks that we need to perform during our animation as **operations**:
```swift
/// Operation that moves a Player to a destination
class PlayerMoveOperation: FlowOperation {
private let player: Player
private let destination: CGPoint
init(player: Player, destination: CGPoint) {
self.player = player
self.destination = destination
}
func perform(completionHandler: @escaping () -> Void) {
self.player.moveTo(self.destination, completionHandler: completionHandler)
}
}
/// Operation that performs a Player attack
class PlayerAttackOperation: FlowOperation {
private let player: Player
init(player: Player) {
self.player = player
}
func perform(completionHandler: @escaping () -> Void) {
self.player.performAttack(completionHandler)
}
}
/// Operation that destroys an enemy
class EnemyDestroyOperation: FlowOperation {
private let enemy: Enemy
init(enemy: Enemy) {
self.enemy = enemy
}
func perform(completionHandler: @escaping () -> Void) {
self.enemy.destroy(completionHandler)
}
}
/// Operation that plays a Player victory animation
class PlayerVictoryOperation: FlowOperation {
private let player: Player
init(player: Player) {
self.player = player
}
func perform(completionHandler: @escaping () -> Void) {
self.player.playVictoryAnimation()
completionHandler()
}
}
```
Secondly; we’ll implement our animation using the above operations:
```swift
let moveOperation = PlayerMoveOperation(player: player, destination: mainEnemy.position)
let attackOperation = PlayerAttackOperation(player: player)
let destroyEnemiesOperation = FlowOperationGroup(operations: enemies.map({
return EnemyDestroyOperation(enemy: $0)
}))
let victoryOperation = PlayerVictoryOperation(player: player)
let operationSequence = FlowOperationSequence(operations: [
moveOperation,
attackOperation,
destroyEnemiesOperation,
victoryOperation
])
operationSequence.perform()
```
While we had to write a bit more code using operations; this approach has some big advantages.
Firstly; we can now use a `FlowOperationGroup` to make sure that all enemy animations are finished before moving on, and by doing this we’ve reduced the state we need to keep within the animation itself.
Secondly; all parts of the animation are now independant operations that don’t have to be aware of each other, making them a lot easier to test & debug - and they could also be reused in other parts of our game.
## API reference
### Protocols
**`FlowOperation`**
Used to declare custom operations.
**`FlowOperationCollection`**
Used to declare custom collections of operations.
### Base operations
**`FlowClosureOperation`**
Operation that runs a closure, and returns directly when performed.
**`FlowAsyncClosureOperation`**
Operation that runs a closure, then waits for that closure to call a completion handler before it finishes.
**`FlowDelayOperation`**
Operation that waits for a certain delay before finishing. Useful in sequences and queues.
### Operation collections & utilities
**`FlowOperationGroup`**
Used to group together a series of operations that all get performed at once when the group is performed.
**`FlowOperationSequence`**
Used to sequence a series of operations, performing them one by one once the sequence is performed.
**`FlowOperationQueue`**
Queue that keeps executing the next operation as soon as it becomes idle. New operations can constantly be added.
**`FlowOperationRepeater`**
Used to repeat operations, optionally using an interval in between repeats.
## How is this different from NSOperations?
`NSOperations` are awesome - and are definetly one of the main sources of inspiration for Flow. However, `NSOperations` are quite heavyweight and can potentially take a long time to implement. Flow was designed to have the power of `NSOperations`, but be a lot easier to use. It’s also written 100% using Swift - making it ideal for Swift-based projects.
## Compatibility
Flow supports all current Apple platforms with the following minimum versions:
- iOS 8
- macOS 10.11
- watchOS 2
- tvOS 9
The current version of Flow supports Swift 3. If you need Swift 2 support, either use [version 1.1](https://github.com/JohnSundell/Flow/releases/tag/1.1), or the [`swift 2` branch](https://github.com/JohnSundell/Flow/tree/swift2).
## Installation
**CocoaPods:**
Add the line `pod "FlowOperations"` to your `Podfile`
**Carthage:**
Add the line `github "johnsundell/flow"` to your `Cartfile`
**Manual:**
Clone the repo and drag the file `Flow.swift` into your Xcode project.
**Swift Package Manager:**
Add the line `.Package(url: "https://github.com/johnsundell/flow.git", majorVersion: 2)` to your `Package.swift`
## Hope you enjoy using Flow!
For support, feedback & news about Flow; follow me on Twitter: [@johnsundell](http://twitter.com/johnsundell).