| Age | Commit message (Collapse) | Author | 
 | 
* cleanup
 | 
 | 
into issue-192-expose-fields-for-options
 | 
 | 
 | 
 | 
 | 
 | 
parameters like e.g. filter or paginate
 | 
 | 
into issue-192-expose-fields-for-options
 | 
 | 
e.g. filter or paginate
 | 
 | 
attribute 'get_serializer'"
 | 
 | 
that it sets them up.
 | 
 | 
 | 
 | 
field metadata via OPTIONS :)
 | 
 | 
into issue-192-expose-fields-for-options
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
git://github.com/grimborg/django-rest-framework into issue-192-expose-fields-for-options
Conflicts:
	rest_framework/tests/fields.py
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Issue 747 lazy strings serialized
 | 
 | 
 | 
 | 
Fix missing min values
 | 
 | 
https://github.com/nschlemm/django-rest-framework/commit/a42afa04c38afe25c9032b8ce37b572678b02cf1#commitcomment-3241476
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
into issue-192-expose-fields-for-options
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
consistently
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
Remove default values - django sets them for us - cause of #710
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
 | 
All relations pointing to ManyToManyFields should default to read-only
 | 
 | 
https://github.com/tomchristie/django-rest-framework/issues/192
missing:
 - get fields for method (currently all the same)
 - tests
 - right placement of code
 | 
 | 
Fix for #710
 | 
 | 
startswith can take a tuple
 | 
 | 
 | 
 | 
 |