Ux
Items Per Page
Page Number
Sorting Order
Sorting Key
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
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)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
No response body
No response body
No content
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
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)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
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)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
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)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
Items Per Page
Page Number
Sorting Order
Sorting Key
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
Serializer for Documents.
Recognized primitve fields:
* ``StringField``
* ``URLField``
* ``EmailField``
* ``IntField``
* ``LongField``
* ``FloatField``
* ``DecimalField``
* ``BooleanField``
* ``DateTimeField``
* ``ComplexDateTimeField``
* ``ObjectIdField``
* ``SequenceField`` (assumes it has integer counter)
* ``UUIDField``
* ``GeoPointField``
* ``GeoJsonBaseField`` (all those fields)
* ``DateField``
Compound fields: ListField and DictField are mapped to corresponding DRF fields, with respect to nested field specification.
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)).
For EmbeddedDocumentField also nested serializer autogenerated for non-zero depth, otherwise it is skipped. TODO: THIS IS PROBABLY WRONG AND SHOULD BE FIXED.
Generic fields GenericReferenceField and GenericEmbeddedDocumentField are handled by their own with corresponding serializer fields.
Not well supported or untested:
``FileField``
``ImageField``
``BinaryField``
All other fields are mapped to DocumentField and probably will work wrong.
trueNo response body
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No response body
No content
No response body
No content
No response body
No content
No response body
No content
No response body
No content
Last updated