| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
consistently
|
|
|
|
|
|
|
|
|
|
|
|
Isn't it nicer to test for a text which is different from
what the previous broken behavior was? Now we can really
tell it works!
|
|
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
|
|
|
|
|
|
|
|
|
|
fix for #765
|
|
|
|
|
|
|
|
|
|
|
|
|
|
when writing. fixes #765
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/tomchristie/django-rest-framework/issues/775
|
|
Allow nested fields to be missing
|
|
|
|
Conflicts:
rest_framework/tests/fields.py
|
|
|
|
Updated the dependencies version and added the ALLOWED_HOSTS for tests.
|
|
|
|
fix function names and dotted lookups for use in PrimaryKeyRelatedField
|
|
HyperlinkedRelatedField. #694
|
|
|
|
|