| { |
| "name": "SegueCoordinator", |
| "version": "0.8.0", |
| "summary": "Keeps your navigation logic separated", |
| "homepage": "https://github.com/npu3pak/ios-lib-segue-coordinator", |
| "license": { |
| "type": "MIT", |
| "file": "LICENSE" |
| }, |
| "authors": { |
| "Evgeniy Safronov": "evsafronov.personal@yandex.ru" |
| }, |
| "source": { |
| "git": "https://github.com/npu3pak/ios-lib-segue-coordinator.git", |
| "tag": "0.8.0" |
| }, |
| "platforms": { |
| "ios": "9.0" |
| }, |
| "swift_versions": "5.0", |
| "source_files": "SegueCoordinator/Classes/**/*", |
| "description": "It is alternative to Application Coordinator pattern.\n\n1. Separates navigation from view controllers.\nControllers no longer need to know anything about other controllers and navigation. If the controller needs to show some data in another controller, it calls a closure and passes data into it. SegueCoordinator handles this closure, shows the desired controller and populates it with data.\n\n2. Removes the boilerplate code.\nSegueCoordinator allows you to perform typical navigation tasks like push, segue, modal in a compact and consistent manner. Also, you can create multiple coordinators for different busines processes and reuse them. SegueCoordinator can become good entry point for this processes." |
| } |
