jarmourato / kodable Goto Github PK

you can remove CRuntime.h and create a CBridge.swift file.
add code to CBridge.swift

import Foundation

@_silgen_name("swift_getTypeByMangledNameInContext")
public func swift_getTypeByMangledNameInContext(
    _ name: UnsafeMutablePointer<Int8>,
    _ nameLength: Int32,
    _ genericContext: UnsafeRawPointer?,
    _ genericArguments: UnsafeRawPointer?)
-> Any.Type?

@_silgen_name("swift_allocObject")
public func swift_allocObject(
    _ type: UnsafeRawPointer?,
    _ requiredSize: Int32,
    _ requiredAlignmentMask: Int32)
-> UnsafeRawPointer?

hope this will helpful!

Original request:

• How to use it in conjunction with CoreData to directly convert JSON data into a new CoreData Entity or update the original Entity. And hope to support CocoaPods

Having KodableTransformable as a class may result in unexpected behaviors, such as the one in the screenshot below:

Properties wrapped in Coding are always reference typed, which causes extra memory management work when dealing with structs. Ideally, KodableTransformable should be a struct.

Hey 👋

While using this framework I found that when encoding optional parameters that have a nil value, those values translate to null values in the resulting JSON, instead of skipping them (as the native Encodable would). This becomes a problem when submitting such JSONs to PATCH endpoints, as the absence of a key-value pair and the presence of the key with a null value have different meanings.

Is there any way to circumvent this that I missed, or is this a bug that needs to be addressed still? 🙏

Looking forward to hearing from you and to continuing using Kodable 🚀

Hey 👋

I've noticed it's extremely hard to understand errors when you face them. Errors from Decodable provide full context on what went wrong, what was expected and what actually happened, whereas Kodable seems to abstract away that info, effectively leaving the developer clueless.

Example:

▿ Kodable.KodableError.invalidValueForPropertyWithKey
  - invalidValueForPropertyWithKey: "message"

When decoding a complex object, a few questions come to mind:

1. Where is message? Which model does it belong to?
2. What was the expected type of message?
3. Sounds like the incoming JSON contains a key named message, but the value wasn't the expected one. What value did the JSON contain, for the message key?

Now, compare the same scenario with the Decodable error:

▿ DecodingError
  ▿ typeMismatch : 2 elements
    - .0 : Swift.String
    ▿ .1 : Context
      ▿ codingPath : 1 element
        - 0 : CodingKeys(stringValue: "message", intValue: nil)
      - debugDescription : "Expected to decode String but found a number instead."
      - underlyingError : nil

Although it doesn't answer questions 1 and 3, it answers 2 pretty clearly, specially with the debugDescription. Perhaps Kodable could incorporate that information and also help answer question 1 and 3, which would increase developers productivity significantly 😊

What do you think @JARMourato ?

Can support CocoaPods?