Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detail the serialization/deserialization in the docs somewhere! #2

Open
mtahmed opened this issue Nov 15, 2013 · 0 comments
Open

Detail the serialization/deserialization in the docs somewhere! #2

mtahmed opened this issue Nov 15, 2013 · 0 comments

Comments

@mtahmed
Copy link
Owner

mtahmed commented Nov 15, 2013

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!)

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

No branches or pull requests

1 participant