Changes between Version 27 and Version 28 of pyson

Timestamp:

05/14/21 14:51:44 (4 years ago)

Author:

wouter

Comment:

--

pyson

@@ -22 +22 @@
 
 == Basic Mechanism
-The basic mechanism for pyson is to look at the __init__ function of the class under serialization.
-The arguments in the __init__ function are matched to the json fields. 
-The arguments in the __init__ must be fully typed, and these types are used to determine how to interpret the json content.
+The basic mechanism for pyson is to look at the {{{__init__}}} function of the class under serialization.
+The arguments in the {{{__init__}}} function are matched to the json fields. 
+The arguments in the {{{__init__}}} must be fully typed, and these types are used to determine how to interpret the json content.
 
+=== Deserialization
+For Deserialization of a json object,  it goes like this
+* if the target class has @JsonSubtypes, 
+ *  check which the subclasses are and what their ID is. 
+ * Determine the actual class contained in the json
+ * "unwrap" the json, so that we have the remaining json to deserialize the actual class
+* If it's not a JsonSubtypes, then the actual class is the requested target class
+* now that the actual class is known, 
+ * the parameter names and param-classes from the {{{__init__}}} function of the actual class are taken 
+ * for each of the parameters, recursively deserialize the json value for that parameter, using the param-class as targetclass.
+ * call the constructor of the target class, using the parsed json for each parameter
 
+=== Serialization
+Serialization of an object is much more straightforward.
+* Create a json dict, with keys the arguments of the __init__ function of the object and the value the serialized value returned by the getter (also considering @JsonGetter)
+* If the object is an instance of a class with @JsonSubtypes, add/wrap the json with class info according to the @JsonTypeInfo 
 
 == Examples