Further notes in 3.0 announcement

This commit is contained in:
Tom Christie 2014-11-19 14:03:19 +00:00
parent 8586290df8
commit 51b7033e4a

View File

@ -821,6 +821,11 @@ Or modify it on an individual serializer field, using the `coerce_to_string` key
The default JSON renderer will return float objects for uncoerced `Decimal` instances. This allows you to easily switch between string or float representations for decimals depending on your API design needs. The default JSON renderer will return float objects for uncoerced `Decimal` instances. This allows you to easily switch between string or float representations for decimals depending on your API design needs.
## Miscellaneous notes.
* The serializer `ChoiceField` does not currently display nested choices, as was the case in 2.4. This will be address as part of 3.1.
* Due to the new templated form rendering, the 'widget' option is no longer valid. This means there's no easy way of using third party "autocomplete" widgets for rendering select inputs that contain a large number of choices. You'll either need to use a regular select or a plain text input. We may consider addressing this in 3.1 or 3.2 if there's sufficient demand.
## What's coming next. ## What's coming next.
3.0 is an incremental release, and there are several upcoming features that will build on the baseline improvements that it makes. 3.0 is an incremental release, and there are several upcoming features that will build on the baseline improvements that it makes.