| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
Issue 747 lazy strings serialized
|
|
Fix missing min values
|
|
|
|
|
|
|
|
|
|
|
|
Remove default values - django sets them for us - cause of #710
|
|
|
|
|
|
|
|
All relations pointing to ManyToManyFields should default to read-only
|
|
Fix for #710
|
|
|
|
|
|
fix for #765
|
|
|
|
|
|
|
|
when writing. fixes #765
|
|
|
|
|
|
|
|
|
|
|
|
Allow nested fields to be missing
|
|
|
|
Conflicts:
rest_framework/tests/fields.py
|
|
|
|
fix function names and dotted lookups for use in PrimaryKeyRelatedField
|
|
HyperlinkedRelatedField. #694
|
|
|
|
|
|
PrimaryKeyRelatedField. #694
|
|
|
|
|
|
According to the [Serializers API Guide][1], `HyperlinkedIdentityField`
takes `lookup_field` as a kwarg like the other related fields and the
generic views. However, this was not actually implemented.
[1]: http://django-rest-framework.org/api-guide/serializers.html#hyperlinkedmodelserializer
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Serializer fields which are themselves serializers should not be required.
Specifically, if a nested object is set to "required=False", it should be
possible to serialize the main object and have the sub-object set to None/null.
|