| { |
| "name": "Closures", |
| "version": "0.5", |
| "summary": "Swifty closures for UIKit and Foundation", |
| "homepage": "https://github.com/vhesener/Closures", |
| "screenshots": [ |
| "https://raw.githubusercontent.com/vhesener/Closures/assets/assets/playground_general.gif", |
| "https://raw.githubusercontent.com/vhesener/Closures/assets/assets/reference_large.png" |
| ], |
| "license": "MIT", |
| "authors": "Vinnie Hesener", |
| "platforms": { |
| "ios": "9.0" |
| }, |
| "source": { |
| "git": "https://github.com/vhesener/Closures.git", |
| "tag": "v0.5" |
| }, |
| "source_files": "Xcode/Closures/Source", |
| "documentation_url": "https://vhesener.github.io/Closures/", |
| "description": "Closures is an iOS Framework that adds closure handlers to many of the popular\nUIKit and Foundation classes. Although this framework is a substitute for \nsome Cocoa Touch design patterns, such as Delegation and Data Sources, and \nTarget-Action, the authors make no claim regarding which is a better way to \naccomplish the same type of task. Most of the time it is a matter of style, \npreference, or convenience that will determine if any of these closure extensions \nare beneficial.\n\nWhether you’re a functional purist, dislike a particular API, or simply just \nwant to organize your code a little bit, you might enjoy using this library.", |
| "pushed_with_swift_version": "4.2" |
| } |
