Tatu Saloranta
Tatu Saloranta
(updated title a bit -- there may be need to support writing of values, too, but that will need different technical solution; two sides are not tightly coupled in this...
I wouldn't think it overly difficult because of Smile codec that does implement it. There are some differences wrt optional array/object length indicators, but overall CBOR codec is bit less...
Unfortunately I can not reproduce this: if I load schema you specify, there is no error. This could either be due to version you are using (if it's old, could...
Thanks! Yes, that does trigger the issue for me too, for 2.8 branch and probably `master` too.
(accidental fix by github, due to comment)
@knoguchi I was hoping to fix this along with #140, as I now understand the issue finally (it has been a while but I got back to here). Scoped resolution...
I don't think anyone has plans for doing that at the moment. Contributions welcome; it would seem like a good thing to do.
I am not sure this is feasible, given that Kryo is more a serialization framework of its own, including databinding, and less a general purpose binary format. So I guess...
@DominicDeCesare-Capita please include a reproduction of what you are doing, how: unfortunately description is bit unclear on what exactly is happening.
Actually I think description is ok. So basically `String` values here should be indicated to be "optional" (String OR null), not mandatory.