Matt Diephouse

I'm okay with this approach if you want to open a PR. :relaxed:

Thanks for the suggestion! I do plan to open things up and add some additional API, but I'm not ready to commit to them yet.

Contributions to the README are definitely welcome

> This should make this a non-breaking change (although users will get a > deprecation warning). There's a caveat here: this isn't a source breaking change, but it _is_ a...

We ran into an issue with this with ReactiveCocoa or ReactiveSwift. I can't find the specific GitHub issue, but @andersio or @ikesyo might remember how to find it. IIRC, it...

> This would only really be an issue if we didn't release this as 5.0, right? I was assuming that the rename changes would come with a 5.0 label because...

> Submodule integration, unless managed by a tool, falls under the "not properly managing your versions" umbrella. These submodules can be managed by Carthage. > Frankly I think SemVer doesn't...

Would it make sense to be generic over some `Value` type instead? `JSON` really is JSON-specific. You might want to work with a different set of primitive types. e.g. if...

> Does it make a difference if you explicitly redeclare `Child` as `Decodable`? ``` error: redundant conformance of 'Child' to protocol 'Decodable' class Child: Parent, Decodable { ^ note: 'Child'...

For now I'm worked around it like this: ```swift struct ChildDecoder { let child: Child init(title: String, subtitle: String) { child = Child(title: title, subtitle: subtitle) } static func decode(_...