SuperCodable
From Foundation
struct AStudent: Codable {
init(from decoder: Decoder) throws {
let container = try decoder.container(keyedBy: CodingKeys.self)
self.aID = try container.decode(String.self, forKey: .aID)
self.aName = try container.decode(String.self, forKey: .aName)
let gradeDecoded = try container.decode(Double.self, forKey: .aGrade)
self.AGrede = Int(gradeDecoded)
}
enum CodingKeys: String, CodingKey {
case aName = "name"
case aGrade = "grade"
case aID = "id"
}
var aID: String
var aName: String
var AGrede: Int
func encode(to encoder: Encoder) throws {
var container = encoder.container(keyedBy: CodingKeys.self)
try container.encode(aID, forKey: .aID)
try container.encode(Double(AGrede), forKey: .aGrade)
try container.encode(aName, forKey: .aName)
}
}
To SuperCodable
{
(double) -> Int in
Int(double)
} toEncoder: { (int) -> Double in
Double(int)
}
">
struct Student: SuperCodable { @Keyed var id: String @Keyed("name") var aName: String @KeyedTransform("grade", doubleTransform) var AGrade: Int } let doubleTransform = SCTransformOf<Int, Double> { (double) -> Int in Int(double) } toEncoder: { (int) -> Double in Double(int) }
Feature
- Working with Nested
Foundation.Codableproperty
Known side effect
- SuperDecoable must construct from nothing
init() @Keyed var id:Intwill do O(n) calculation on underlaying wrapper_VARIABLE_NAMEinto keyVARIABLE_NAME. Be ware of variable name takes too long
Known Disability
- Every property in a SuperCodable should a
DecodableKey/EncodableKey, otherwise the property(which should beCodable) will simply ignored during the Codable process.
Why:
Basically Mirror can't mutating the object value during the
init(from decoder:) throws, since we create the object fromself.init()
Other notes
-
Inspired by: https://medium.com/trueid-developers/combined-propertywrapper-with-codable-swift-368dc4aa2703
-
Try to merge
@KeyedTransforminto@Keyed, but it required@Keyed var id: Stringto be@Keyed() var id: String, with extra()🧐 -
Swift should auto generate
STRUCT.init(....)for you, but if you using@Keyed var id: Stringwithout default value, it will generateinit(id: Keyed, by giving default value) @Keyed var id: String = ""should solve this problem.
Know Issues
@Keyed var id:String?will cause fatalError on force unwrappingKeyed.value?, you can using@OptionalKeyedto make it works.OptionalKeyedmay / may not a good name, I am thinking of make the easy to change, maybeKeyedOptionalis EASY change?🤔
91 Oct 23, 2022
2 Aug 17, 2022
2 Nov 20, 2022
17 Jun 27, 2022
22 Nov 9, 2022
10 Apr 24, 2022
0 Oct 7, 2021
1 May 3, 2022
0 Nov 8, 2021
0 Dec 15, 2021
27 Apr 8, 2022
130 Nov 8, 2022
509 Jun 29, 2022
472 Dec 18, 2022
4 Mar 21, 2022
1 Nov 19, 2021
0 Nov 30, 2021
1 Apr 20, 2022
14 Sep 27, 2022