Open scott-wilson opened 6 months ago
Two things:
Two things:
- we probably want to look at what the serde xml parsers do here, because children can mean different things and it needs to be configurable
- We should wait until #70 lands to do this, since that’s going to break a lot of stuff
That seems fine by me. I expect it to be a bit of a challenge tbh but that might be because I’ve never implemented a serde thing before.
Same, haven't implemented serde before. But, that's the fun! We'll learn how to implement it together!
Another useful reference might be Kaydle: https://github.com/Lucretiel/kaydle, which is the last attempt I know of of someone trying to serdeify kdl, and they did some interesting things, just never finished it (it's a big project, it turns out!)
although part of the reason Kaydle was big was because it wrote its own parser and it was being fancy about it. With kdl-rs you'd only really need to convert the KdlDocument
struct through serde.
sigh. I think this is going to need a completely new parser. Can I just catch a break lmao.
This is another crack at Serde support (linking #17 for historical reference).
The basic API that I'm thinking of would look something like this (borrowing from Serde JSON):
If no one has an issue, I'd be happy to take this on.