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
Currently it's ambiguous and there might be caveats that are not easily decipherable from the code.
For example currently, only classes that have the init arguments "stored" in them as attributes are "properly" serialized and deserialized because those attributes are used for initialization. This should be documented somewhere.
TODO: We should allow not storing the init arguments and instead allow creating empty objects with attributes injected later. This would require e.g. having no mandatory arguments etc. or using some trickery to bypass init by call new directly etc. (NOT IDEAL!)
The text was updated successfully, but these errors were encountered:
Currently it's ambiguous and there might be caveats that are not easily decipherable from the code.
For example currently, only classes that have the init arguments "stored" in them as attributes are "properly" serialized and deserialized because those attributes are used for initialization. This should be documented somewhere.
TODO: We should allow not storing the init arguments and instead allow creating empty objects with attributes injected later. This would require e.g. having no mandatory arguments etc. or using some trickery to bypass init by call new directly etc. (NOT IDEAL!)
The text was updated successfully, but these errors were encountered: