Closed Darkle closed 12 months ago
Hi there @Darkle I believe this might an issue with how the serializer on the dotnet client is setup, it should not infer anything from strings, something like DateTimeHandling.None
on the serializer options. I need to check that
Fixed as of Fable.Remoting.DotnetClient v3.32 :rocket: it was indeed the date parse handling that needed to be disabled. Thanks a lot for filing the issue and for the detailed report. Please take the new package for a spin and see if it fixes the issue. I expect that it is resolved but feel free to re-open if the problem persists
Wow, thanks so much for the quick response! I just tried the updated version and it indeed does fix the issue.
Cheers.
Hi, I seem to be encountering an issue with the fable remoting dotnet client deserialization of strings when the string looks like an ISO date string.
With the following types:
and the following server code:
and the following client code:
I get the following output:
You can see that the api route that returns the post inside of a Result alters the string. It seems like it infers that it is an ISO date string and parses it as a date, then converts it back to a string.
Repo here: https://github.com/Darkle/fable-remoting-issue
Details:
I searched through previous issues, perhaps this is related: https://github.com/Zaid-Ajaj/Fable.Remoting/issues/304