encode/django-rest-framework
1
1
Fork 0
mirror of https://github.com/encode/django-rest-framework.git synced 2025-08-04 12:30:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

Edits to announcement

Browse Source
This commit is contained in:
Carlton Gibson 2018-03-26 11:30:30 +02:00
parent 761a034441
commit cfa942ffc1
1 changed files with 13 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
docs/topics/3.8-announcement.md
View File

@ -19,9 +19,8 @@
# Django REST framework 3.8 # Django REST framework 3.8
TODO The 3.8 release is a maintenance focused release resolving a large number of previously outstanding issues and laying
the foundations for future changes.
The 3.8 release ...
--- ---
@ -33,18 +32,17 @@ If you use REST framework commercially and would like to see this work continue,
*We'd like to say thanks in particular our premium backers, [Rover](http://jobs.rover.com/), [Sentry](https://getsentry.com/welcome/), [Stream](https://getstream.io/?utm_source=drf&utm_medium=banner&utm_campaign=drf), [Machinalis](https://hello.machinalis.co.uk/), and [Rollbar](https://rollbar.com).* *We'd like to say thanks in particular our premium backers, [Rover](http://jobs.rover.com/), [Sentry](https://getsentry.com/welcome/), [Stream](https://getstream.io/?utm_source=drf&utm_medium=banner&utm_campaign=drf), [Machinalis](https://hello.machinalis.co.uk/), and [Rollbar](https://rollbar.com).*
--- ---
## Breaking Changes ## Breaking Changes
### Altered behaviour of `read_only` plus `default` on Field. ### Altered the behaviour of `read_only` plus `default` on Field.
[#5886][gh5886] [#5886][gh5886] `read_only` fields will now **always** be excluded from writable fields.
`read_only` fields will now **always** be excluded from writable fields. Previously `read_only` fields when combined with a `default` value would use the `default` for create and update
operations. This was counter-intuitive in some circumstances and led to difficulties supporting dotted `source`
Previously `read_only` fields with a `default` value would use the `default` for create and update operations. attributes on nullable relations.
In order to maintain the old behaviour you may need to pass the value of `read_only` fields when calling `save()` in In order to maintain the old behaviour you may need to pass the value of `read_only` fields when calling `save()` in
the view: the view:
@ -54,33 +52,6 @@ the view:
Alternatively you may override `save()` or `create()` or `update()` on the serialiser as appropriate. Alternatively you may override `save()` or `create()` or `update()` on the serialiser as appropriate.
---
## Boolean Composable Permissions
TODO
---
## Namespace Support
TODO
---
## Viewset actions
TODO:
---
## Minor fixes and improvements
There are a large number of minor fixes and improvements in this release. See the [release notes](release-notes.md) page for a complete listing.
--- ---
## Deprecations ## Deprecations
@ -89,6 +60,12 @@ TODO
--- ---
## Minor fixes and improvements
There are a large number of minor fixes and improvements in this release. See the [release notes](release-notes.md) page
for a complete listing.
## What's next ## What's next
TODO TODO