Serialization Help #386
Unanswered
shay-aharonson
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some general implementation and & architectural questions here.
Just started fooling around with this lib, as I've come to understand every class member must implement serializable per the documentation, while non serializable objects are to be injected in composable functions locally.
Can someone please explain to me the idea behind forcing everything to be serializable?
I feel this clutters and boilerplates lots of code. Every function now needs to declare all these new local params that were class members and could easily be reinitialized in init{} or relevant lifecycle methods. Wouldn't it be possible to do the same here? Why not have an annotation to not serialize chosen class members and have them initialized manually?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions