Why is ISet not supported? about aqlaserializer HOT 10 CLOSED

Also, does Aqla support IReadOnlyDictionary, IReadOnlyCollection, IReadOnlySet?

from aqlaserializer.

You are right, they must be supported. They simply did not exist at the time of active development of AqlaSerializer. I'm going to add support for them some time later.

from aqlaserializer.

The complicated thing here is that non generic ICollection doesn't have an Add method so I had to use IList.

from aqlaserializer.

Is there any updates on this issue? When can we get the solution for it?

from aqlaserializer.

It turned out to be easier than I thought. I already have a working implemention of ISet support.

from aqlaserializer.

I uploaded a new version with all these interfaces supported. Please confirm that it works on your side.

from aqlaserializer.

It works at interface level. However, what I serialized type is different from the deserialized type:
System.Collections.ObjectModel.ReadOnlyCollection -> System.Collections.Generic.List
System.Collections.ObjectModel.ReadOnlyDictionary<string, int> -> System.Collections.Generic.Dictionary<string, int>

Is it possible to deserialize back the same type as serialized?

from aqlaserializer.

No, but you can make surrogates for them. What is your usage scenario so that you care about underlying type? In OOP you should not downcast things, you are expected to use them only by provided interfaces.

from aqlaserializer.

We have unit tests which compare the objects before and after serialization. The comparison verifies the object types to make sure that through deep cloning, we get exactly the same object back.

from aqlaserializer.

Ok. As I said you can use surrogates to hook into serialization process.

I don't see how type changing like this may cause an issue in a real app so I'm closing this.

from aqlaserializer.