encode/django-rest-framework
1
1
Fork 0
mirror of https://github.com/encode/django-rest-framework.git synced 2025-07-11 16:52:31 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated Getting to 1.0 (markdown)

tomchristie 2012-02-16 01:19:10 -08:00
parent dc81db4916
commit adf146c541
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Getting-to-1.0.md

@ -30,7 +30,7 @@ Stuff that needs to change
+ Provide a `reverse` call that extends the standard `reverse`, + Provide a `reverse` call that extends the standard `reverse`,
but can take the current request as an argument if an absolute URL is required. but can take the current request as an argument if an absolute URL is required.
7. Hooks throughout for creating `.resource`, `.serializer`, `.renderer` etc... instances inside the View, given the classes. 7. Hooks throughout for creating `.resource`, `.serializer`, `.renderer` etc... instances inside the View, given the classes.
8. Drop support for unnamed args in URLs filtering as pk. Better to always be explicit in the urlconf. 8. Drop support for unnamed args in URLs filtering as pk. Better to always be explicit in the urlconf. **DONE**
9. `InstanceMixin` needs to disappear. 9. `InstanceMixin` needs to disappear.
10. `.CONTENT` probably needs to disappear. To confusing to have that as well as `.DATA` and `.FILES`. 10. `.CONTENT` probably needs to disappear. To confusing to have that as well as `.DATA` and `.FILES`.
11. Explorable JSON: The default JSON output could have a section for placing meta information either by default or by swapping in a new serializer. This is common in REST API's as a place to give clients things such as type information, pagination links, etc... Two approaches seem to make sense: a Tastypie compatible approach ( with a meta dict and objects list) or something like the well-regarded foursquare API (with meta, and response dicts) (@poswald) 11. Explorable JSON: The default JSON output could have a section for placing meta information either by default or by swapping in a new serializer. This is common in REST API's as a place to give clients things such as type information, pagination links, etc... Two approaches seem to make sense: a Tastypie compatible approach ( with a meta dict and objects list) or something like the well-regarded foursquare API (with meta, and response dicts) (@poswald)