| { |
| "name": "SwiftRepository", |
| "version": "0.4.5", |
| "summary": "Essentially, provides an abstraction of data access", |
| "description": "The simplest approach, especially with an existing system, is to create a new Repository implementation for each business object you need to store to or retrieve from your persistence layer. Further, you should only implement the specific methods you are calling in your application. Avoid the trap of creating a “standard” repository class, base class, or default interface that you must implement for all repositories. Yes, if you need to have an Update or a Delete method, you should strive to make its interface consistent (does Delete take an ID, or does it take the object itself?), but don’t implement a Delete method on your LookupTableRepository that you’re only ever going to be calling List() on. The biggest benefit of this approach is YAGNI – you won’t waste any time implementing methods that never get called.", |
| "homepage": "https://github.com/dsay/Repository", |
| "license": { |
| "type": "MIT", |
| "file": "LICENSE" |
| }, |
| "authors": { |
| "Dima Sai": "dmitriy.sai2013@gmail.com" |
| }, |
| "source": { |
| "git": "https://github.com/dsay/Repository.git", |
| "tag": "0.4.5" |
| }, |
| "platforms": { |
| "ios": "11.0" |
| }, |
| "source_files": "Repository/**/*", |
| "swift_versions": "5.0", |
| "frameworks": "UIKit", |
| "dependencies": { |
| "RealmSwift": [ |
| |
| ], |
| "PromiseKit/CorePromise": [ |
| |
| ], |
| "AlamofireObjectMapper": [ |
| |
| ] |
| }, |
| "swift_version": "5.0" |
| } |
