Skip to content

Conversation

object
Copy link
Contributor

@object object commented Apr 20, 2016

I made the changes a bit in the blind because there don't seem to be any tests that trigger the affected code. All F# API tests pass, and I verified that the sample program PersistenceExample.FsApi work just as it worked before. Now it works with both JSON.NET and Wire serializer, before F# persistence wrapper expected only JSON.NET. But even using PersistenceExample.FsApi I was not able to test all code branches.

If you find something that doesn't work with the proposed changes, please let me know how I can reproduce the problem and I will try to fix it.

match Serialization.tryDeserializeJObject serializer.Serializer msg with
| Some(e) -> state <- aggregate.apply mailbox state e
| None -> x.Unhandled msg
let serializer = UntypedActor.Context.System.Serialization.FindSerializerForType typeof<obj>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't that be typeof<'Event>?

@object
Copy link
Contributor Author

object commented Apr 20, 2016

I thought so too, that is should use concrete types instead of obj. But since I am new to the code base I wanted to be very conservative about changes and left the original code untouched as much as I could. But now that you pointed this out - yes I agree. It should be the actual types - 'Event, 'Command etc.

@object
Copy link
Contributor Author

object commented Apr 22, 2016

Corrected type cast.

@Horusiath
Copy link
Contributor

It looks like we have some FAKE problems. /cc @Aaronontheweb

@marcpiechura
Copy link
Contributor

@object you need to rebase with latest dev, that should fix the build problems

@object
Copy link
Contributor Author

object commented Apr 28, 2016

Will do, thanks.

Willem Meints and others added 7 commits April 28, 2016 12:22
Added some basic specs for the mailbox/actor combinations in Akka.NET.
Bounded dispatcher and mailbox configurations haven't been added yet
as these are not supported right now.

Takes care of issue #1793
@object
Copy link
Contributor Author

object commented Apr 28, 2016

@Silv3rcircl3 @Horusiath I rebased my changes, should be OK now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants