Deserialization not invoking processors when actual type != storage type about fullserializer HOT 4 CLOSED

Just saw the latest commit and looks like you are aware of the issue and are considering using object type to fetch processors. I would like to make an argument for the case.

A common use case is that multiple classes, derived from the same class or implementing same interface, can be serialized/deserialized using the same code without having to write custom handlers for each class (passing the base class/interface as container). In this case processors will be called while serializing but not while deserializing and this is inconsistent.

Thanks for reading.

from fullserializer.

Yes, I think using the object type is the correct approach. I'll switch the code to use that in the future in the near future.

from fullserializer.

Has this been implemented yet? I'm having a similar issue.

from fullserializer.

This fix may break NodeCanvas, though I don't think it will. Checking with @nuverian.

from fullserializer.