Loïc Denuzière
Loïc Denuzière
Ah, this is bad indeed. It looks like the path is handled by passing a string to `JsonException`, so this shouldn't be too difficult to fix.
So, as it turns out, this is not currently possible. Even if I catch the exception and raise a new one with a correct path, the exception gets mutated by...
As far as I can tell from reading the source of S.T.J, that's right.
> Just checking, would it do the same for `Error`? Presumably yeah. > Another option could be to add a TryExec and return a result (FSharp.Core.Result). You'd have to match...
That's odd, at first glance I don't see why changing the OutputType should change anything regarding System.Text.Json. I'll try to see if I can reproduce.
When DU cases are external, their naming should conform to the policy specified in the main options.
That's an interesting conundrum, because really they're both union tags and properties. I definitely see your point. At the same time, having the same type print as `"Pending"` and `{"available":10}`...
There is no support for partial values, but you can put several names explicitly: `[]`.
Some features of FSharp.SystemTextJson could be implemented using this API, but as far as I can tell, it doesn't seem flexible enough for all features. For example, it looks like...
Good call, I think this should even be the default.
I pasted your code into fsi and it correctly returned `Some MissingScope` for the last line. What versions of .NET and FSharp.SystemTextJson are you using?