| Age | Commit message (Collapse) | Author | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
sprymak-master
 | 
 | 
 | 
 | 
URL_FIELD_NAME setting
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
* base classes define it with one parameter
* BaseSerializer currently defines a second parameter, which we make optional here for method-dispatch passivity
 | 
 | 
 | 
 | 
 | 
 | 
Fix infered field type for models.NullBooleanField
 | 
 | 
source set.
 | 
 | 
 | 
 | 
Fixed the nested model serializers in case of the related_name isn’t set...
 | 
 | 
cases.  Closes #1205
 | 
 | 
required RelatedField to null (issue #1158)
 | 
 | 
isn’t set on the ForeignKey.
 | 
 | 
 | 
 | 
 | 
 | 
Fix object creation with reverse M2M when related_name unspecified
 | 
 | 
It seems that field.related_query_name() does not return the related_name
for reverse M2M relations when related_name is not explicitly set in the M2M field
definition.
So, change to use obj.get_accessor_name(), where obj is an instance of
RelatedObject, as are returned by a model's
_meta.get_all_related_many_to_many_objects(), or as in the tuples returned by
_meta.get_all_m2m_objects_with_model().
 | 
 | 
 | 
 | 
The empty value defaults back to '' (for backwards-compatibility) but
is changed automatically to None for ModelSerializers if the `null`
property is set on the db field.
 | 
 | 
browsable API
 | 
 | 
fix writing into foreign key with non-null source
 | 
 | 
Test case and fix for issue 1111
 | 
 | 
 | 
 | 
The error occurs when serializer is set with partial=True and a
field-level validation is defined on a field, for which there's no
corresponding update value in .data
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Feature: add transform_<fieldname> methods to serializers
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
opposite of validate_<fieldname> on a per-field basis.
 | 
 | 
 | 
 | 
 | 
 | 
parameterize identity field serializer class to allow for easier subclassing
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 |