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
Replacement of DRF ModelSerializer, with almost the same API and features.
99
-
100
-
Regocnized primitve fields:
101
-
102
-
``StringField``
103
-
``URLField``
104
-
``EmailField``
105
-
``IntField``
106
-
``LongField``
107
-
``FloatField``
108
-
``DecimalField``
109
-
``BooleanField``
110
-
``DateTimeField``
111
-
``ComplexDateTimeField``
112
-
``ObjectIdField``
113
-
``SequenceField`` (assumes it has integer counter)
114
-
``UUIDField``
115
-
``GeoPointField``
116
-
``GeoJsonBaseField`` (all those fields)
117
-
118
-
Compound fields: ``ListField`` and ``DictField`` mapped to corresponding DRF fields, with respect to nested field specification.
119
-
120
-
The ``ReferenceField`` is handled like ``ForeignKey`` in DRF: there nestted serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as ``str(id)``.
98
+
Recognized primitve fields:
99
+
100
+
* ``StringField``
101
+
* ``URLField``
102
+
* ``EmailField``
103
+
* ``IntField``
104
+
* ``LongField``
105
+
* ``FloatField``
106
+
* ``DecimalField``
107
+
* ``BooleanField``
108
+
* ``DateTimeField``
109
+
* ``ComplexDateTimeField``
110
+
* ``ObjectIdField``
111
+
* ``SequenceField`` (assumes it has integer counter)
112
+
* ``UUIDField``
113
+
* ``GeoPointField``
114
+
* ``GeoJsonBaseField`` (all those fields)
115
+
116
+
Compound fields: ``ListField`` and ``DictField`` are mapped to corresponding DRF fields, with respect to nested field specification.
117
+
118
+
The ``ReferenceField`` is handled like ``ForeignKey`` in DRF: there nested serializer autogenerated if serializer depth greater then 0, otherwise it's handled by it's own (results as ``str(id)``).
121
119
122
120
For ``EmbeddedDocumentField`` also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
0 commit comments