| { |
| "name": "VBCoordinator", |
| "version": "1.2.0", |
| "summary": "Implementation of Mediator pattern to control screens flow.", |
| "description": "Implementation of Mediator pattern to control screens flow.\n\nCheck these articles https://medium.com/blacklane-engineering/coordinators-essential-tutorial-part-i-376c836e9ba7 and https://medium.com/blacklane-engineering/coordinators-essential-tutorial-part-ii-b5ab3eb4a74 to get the idea of what coordinator is.\n\nIn short, a coordinator is a mediator between several screens or between other coordinators (screens flow). It opens ViewControllers and other coordinators. All screens are developed to be totally independent from each other. A ViewController is never opened from another one - only coordinator should do this. \n\nYou create a hierarchy of coordinators starting with the AppCoordinator. He \"knows\" which flow should be first depending on situation.", |
| "homepage": "https://github.com/valnoc/Coordinator", |
| "license": "MIT", |
| "authors": { |
| "Valeriy Bezuglyy": "valnocorner@gmail.com" |
| }, |
| "source": { |
| "git": "https://github.com/valnoc/Coordinator.git", |
| "tag": "1.2.0" |
| }, |
| "swift_versions": "5.2", |
| "platforms": { |
| "ios": "9.0" |
| }, |
| "requires_arc": true, |
| "source_files": "Sources/**/*", |
| "swift_version": "5.2" |
| } |
