You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// let response = aref <? msg |> Async.RunSynchronously
// response
// |> equals msg
I think a lot of this stems from the Akka.NET v1.3 push and the fact that F# lagged behind a bit on .NET Core support at the time. Now that everything is pretty reliable there for the most part we should reintroduce these tests as part of our suite.
Actual behavior
Not sure, but it looks like the DU content is lost in translation.
Expected behavior
DUs should be serializable via:
Newtonsoft.Json
Hyperion
With all of its contents correctly preserved.
The text was updated successfully, but these errors were encountered:
* added reproduction for DU serialization
close#5194
* exposed `exprSerializationSupport` to public
* validated that record-based serialization works out of the box
* added dedicated serialization specs
* cleaned up RemoteSpecs and SerializationSpecs
Now checking for whether or not manifests are emitted
* added hardened test case to validate that DU serialization does not work
* added spec that proves this is a Newtonsoft.Json issue
* restored common.props
* disabled JSON.NET repro spec
* migrated to using Hyperion for DU tests
* removed bad test
Version Information
Version of Akka.NET? v1.4.23
Which Akka.NET Modules? Akka.FSharp
Describe the bug
https://stackoverflow.com/questions/68741561/akka-unable-to-send-discriminated-unions-as-messages-in-f#comment121522181_68741561 - looks like default DU serialization isn't working with Newtonsoft.Json per this user's report.
As it so happens, our DU serialization tests are out of date and commented out:
akka.net/src/core/Akka.FSharp.Tests/ApiTests.fs
Lines 41 to 76 in d146387
I think a lot of this stems from the Akka.NET v1.3 push and the fact that F# lagged behind a bit on .NET Core support at the time. Now that everything is pretty reliable there for the most part we should reintroduce these tests as part of our suite.
Actual behavior
Not sure, but it looks like the DU content is lost in translation.
Expected behavior
DUs should be serializable via:
With all of its contents correctly preserved.
The text was updated successfully, but these errors were encountered: