Johannes Lund
Johannes Lund
Added a `0.4.2` tag for now at least.
Changed it from `0.5` to `0.5.0`. Hope that helps. Thanks!
Oh, it already is. Really have no concrete ideas, so removing from 1.0 milestone.
I'm open to renaming, but I think unification with `Codable` should be explored first. Import boilerplate might be ugly and confusing, but `Deco.Decodable` and `Swift.Decodable` just being different, seems to...
+1 on the performance point, I assumed Swift.Decodable was fast before that. In that case I would propose to release a new version in time for Swift 4.1 with something...
More concrete first steps: - Store references to each dictionary inside the Error, not just the path - Create custom string representations using this Personally I think some kind of...
Haven't used Core Data in a long, long time, but could something like this work? ``` swift class Test: NSManagedObject { @NSManaged var foo: String static func decode(json: AnyObject) throws...
Though perhaps your question was on Core Data-best-practice, and if so, I do not know.
I imagined copy-pasting code as an acceptable solution here if the code could be kept short. Maybe there is some problem with this I haven't thought about, but moving the...
Haven't thought about doing it automatically. I'm afraid it would be difficult to do unless changing the fundamental decoding approach to something more like [Hearst-DD/ObjectMapper](https://github.com/Hearst-DD/ObjectMapper). If not doing it automatically...