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
I have a couple of classes that should be serialized/deserialized in the same way. Therefore I wrote a common base class with serialization/deserialization methods and @HandlerCallback annotation. This one works as expected.
However, extended classes (with no additional properties) seem to ignore those @HandlerCallbacks and get serialized as if those methods didn't exist.
Is this the expected behaviour?
If so, the documentation should reflect this behaviour. But actually inheriting @HandlerCallbacks would IMHO seem to be more 'in style' (see also e.g. JsonSerializable)
The text was updated successfully, but these errors were encountered:
I have a couple of classes that should be serialized/deserialized in the same way. Therefore I wrote a common base class with serialization/deserialization methods and @HandlerCallback annotation. This one works as expected.
However, extended classes (with no additional properties) seem to ignore those @HandlerCallbacks and get serialized as if those methods didn't exist.
Is this the expected behaviour?
If so, the documentation should reflect this behaviour. But actually inheriting @HandlerCallbacks would IMHO seem to be more 'in style' (see also e.g. JsonSerializable)
The text was updated successfully, but these errors were encountered: