Loïc Denuzière
Loïc Denuzière
Yes, it is on purpose that None and ValueNone are serialized as null. I am open to adding an option to customize this though!
I would be curious to see your actual use case in more detail. Mutually recursive *types* work fine, for example: ```fsharp type A = { b: B option } and...
The idea behind failing on missing fields is that this is more likely to be a data authoring error than an intentional feature. But I can see that in a...
Got struct record serialization working, with similar results: ``` BenchmarkDotNet=v0.11.5, OS=Windows 10.0.18362 Intel Core i7-6700 CPU 3.40GHz (Skylake), 1 CPU, 8 logical and 4 physical cores .NET Core SDK=3.0.100-preview7-012821 [Host]...
Yeah, I've considered publishing this as an emit-based non-allocating alternative to `FSharp.Reflection`. I need to at least implement it for unions though, and it's harder than records 🙂
This looks like a nice improvement, thanks for the heads up @baronfel !
As the author of Bolero, which runs on WebAssembly, I fully agree that environments where `Emit` is unavailable must and will always remain supported! That being said, as you can...
When serializing a field type that it doesn't explicitly handle, this library just hands it over to System.Text.Json. So that's indeed why null strings are serialized as null. The deserializer...
I don't think there's anything better to do if you want to handle this within the serialization layer.
`.WithAllowOverride()` should do what you need here.