Add proof of concept for Thot.Json code generation #17
Add proof of concept for Thot.Json code generation #17
Conversation
Don't look at |
Oups, I looked at Thanks for the code, I will play a bit with it :) |
Let me know if you need some complex encoding / decoding examples, I have a few spots I'm converting to |
@jgrund Are you using custom decoders ? In my complexe structure, I am using some of them for decoding Date for example. I wonder, if I should not add an extension to Thot.Json for common decoders like that. |
Date seems like something that could be configurable on the encoding side at least (different consumers may work with different datetime representations). I'm converting a bunch of code from |
Oh I don't think I have recursive DU in my code base so yes if you can share some types that could help us :) |
https://github.com/intel-hpdd/rust-libzfs/blob/master/Fable.Import.NodeLibzfs/fable/NodeLibzfs.fs Has a bunch of types I just converted to use |
Awesome thank you :) I am abusing, if I ask for a json ? I didn't look at the repo to see if it's easy to produce one or no. |
Sure, we have tests that are covering everything here (and have JSON strings that are being decoded): https://github.com/intel-hpdd/rust-libzfs/blob/master/Fable.Import.NodeLibzfs/test/NodeLibzfs.Test.fs And generated snapshots for the output here (that have JSON strings output from encoding): https://github.com/intel-hpdd/rust-libzfs/blob/master/Fable.Import.NodeLibzfs/test/__snapshots__/NodeLibzfs.Test.fs.snap |
faa5ee5
to
ff793cd
Compare
I am closing in favor of #20 , I already started a discussion with Krys about that. |
Instructions :)