Separate Decodable and Encodable? about bettercodable

[marksands]

💯 I will see what I can do.

[entropious]

Hi. Any progress on this? I have the same problem with LossyArray. Don't know why T is restricted to Codable in current implementation. If LossyArray is implemented like this, it will support both Codable and Decodable.

@propertyWrapper
public struct LossyArray<T: Decodable>: Decodable {
    private struct AnyDecodableValue: Decodable {}
    private struct LossyDecodableValue<Value: Decodable>: Decodable {
        let value: Value
        
        public init(from decoder: Decoder) throws {
            let container = try decoder.singleValueContainer()
            value = try container.decode(Value.self)
        }
    }
    
    public var wrappedValue: [T]
    
    public init(wrappedValue: [T]) {
        self.wrappedValue = wrappedValue
    }
    
    public init(from decoder: Decoder) throws {
        var container = try decoder.unkeyedContainer()
        
        var elements: [T] = []
        while !container.isAtEnd {
            do {
                let value = try container.decode(LossyDecodableValue<T>.self).value
                elements.append(value)
            } catch {
                _ = try? container.decode(AnyDecodableValue.self)
            }
        }
        
        self.wrappedValue = elements
    }
    
}

[lordzsolt]

Don't know why T is restricted to Codable in current implementation.

Answering just this part. @LossyArray supports encoding as well, which your code doesn't.

Some people might want that feature.

[yonaskolb]

Keen to see this too. I think this should be possible to implement with extensions instead similar to how Equatable and Hashable are handled

extension DefaultCodable: Decodable where Default.DefaultValue: Decodable {
...
 }
extension DefaultCodable: Encodable where Default.DefaultValue: Encodable {
...
 }

[yonaskolb]

PR here #38