When calling valueOptional with a value that might return null,
value method is called, value tries to decode a given keyPath, if the keyPath is null(which is logically correct since I called valueOptional),
value throws on DecodeError.missingKeyPath, which triggers swift exception break point.
Is there any future plans in solving this issue? maybe leading valueOptional through a different end point?
When calling valueOptional with a value that might return null,
valuemethod is called,valuetries to decode a given keyPath, if the keyPath is null(which is logically correct since I called valueOptional),valuethrows onDecodeError.missingKeyPath, which triggers swift exception break point.Is there any future plans in solving this issue? maybe leading valueOptional through a different end point?