Commit beeb6d58 by Tom Christie

Update documentation

parent 144701c8
...@@ -431,8 +431,8 @@ ...@@ -431,8 +431,8 @@
</p> </p>
<hr /> <hr />
<p><strong>Note</strong>: This is the documentation for the <strong>version 3.1</strong> of REST framework. Documentation for <a href="http://tomchristie.github.io/rest-framework-2-docs/">version 2.4</a> is also available.</p> <p><strong>Note</strong>: This is the documentation for the <strong>version 3.2</strong> of REST framework. Documentation for <a href="http://tomchristie.github.io/rest-framework-2-docs/">version 2.4</a> is also available.</p>
<p>For more details see the <a href="topics/3.1-announcement/">3.1 release notes</a>.</p> <p>For more details see the 3.2 <a href="topics/3.2-announcement/">announcement</a> and <a href="topics/release-notes/">release notes</a>.</p>
<hr /> <hr />
<p> <p>
<h1 style="position: absolute; <h1 style="position: absolute;
......
...@@ -342,6 +342,10 @@ ...@@ -342,6 +342,10 @@
</li> </li>
<li> <li>
<a href="#supported-versions">Supported versions</a>
</li>
<li>
<a href="#deprecations">Deprecations</a> <a href="#deprecations">Deprecations</a>
</li> </li>
...@@ -387,6 +391,9 @@ ...@@ -387,6 +391,9 @@
<p>There are some limitations to the <code>AdminRenderer</code>, in particular it is not yet able to handle list or dictionary inputs, as we do not have any HTML form fields that support those.</p> <p>There are some limitations to the <code>AdminRenderer</code>, in particular it is not yet able to handle list or dictionary inputs, as we do not have any HTML form fields that support those.</p>
<p>Also note that this is an initial release and we do not yet have a public API for modifying the behavior or documentation on overriding the templates.</p> <p>Also note that this is an initial release and we do not yet have a public API for modifying the behavior or documentation on overriding the templates.</p>
<p>The idea is to get this released to users early, so we can start getting feedback and release a more fully featured version in 3.3.</p> <p>The idea is to get this released to users early, so we can start getting feedback and release a more fully featured version in 3.3.</p>
<h2 id="supported-versions">Supported versions</h2>
<p>This release drops support for Django 1.4.</p>
<p>Our supported Django versions are now 1.5.6+, 1.6.3+, 1.7 and 1.8.</p>
<h2 id="deprecations">Deprecations</h2> <h2 id="deprecations">Deprecations</h2>
<p>There are no new deprecations in 3.2, although a number of existing deprecations have now escalated in line with our deprecation policy.</p> <p>There are no new deprecations in 3.2, although a number of existing deprecations have now escalated in line with our deprecation policy.</p>
<ul> <ul>
...@@ -419,7 +426,7 @@ ...@@ -419,7 +426,7 @@
</ul> </ul>
<p>The upshot is this: If you have many to many fields in your models, then make sure you've included the argument <code>blank=True</code> if you want to allow empty inputs in the equivalent <code>ModelSerializer</code> fields.</p> <p>The upshot is this: If you have many to many fields in your models, then make sure you've included the argument <code>blank=True</code> if you want to allow empty inputs in the equivalent <code>ModelSerializer</code> fields.</p>
<h3 id="list-fields-and-allow_null">List fields and allow_null</h3> <h3 id="list-fields-and-allow_null">List fields and allow_null</h3>
<p>When using <code>allow_null</code> with <code>ListField</code> or a nested <code>mant=True</code> serializer the previous behavior was to allow <code>null</code> values as items in the list. The behavior is now to allow <code>null</code> values instead of the list.</p> <p>When using <code>allow_null</code> with <code>ListField</code> or a nested <code>many=True</code> serializer the previous behavior was to allow <code>null</code> values as items in the list. The behavior is now to allow <code>null</code> values instead of the list.</p>
<p>For example, take the following field:</p> <p>For example, take the following field:</p>
<pre><code>NestedSerializer(many=True, allow_null=True) <pre><code>NestedSerializer(many=True, allow_null=True)
</code></pre> </code></pre>
......
...@@ -406,6 +406,14 @@ ...@@ -406,6 +406,14 @@
</code></pre> </code></pre>
<hr /> <hr />
<h2 id="32x-series">3.2.x series</h2> <h2 id="32x-series">3.2.x series</h2>
<h3 id="321">3.2.1</h3>
<p><strong>Date</strong>: <a href="https://github.com/tomchristie/django-rest-framework/issues?q=milestone%3A%223.2.1+Release%22">7th August 2015</a>.</p>
<ul>
<li>Fix for relational select widgets rendering without any choices. (<a href="https://github.com/tomchristie/django-rest-framework/issues/3237">#3237</a>)</li>
<li>Fix for <code>1</code>, <code>0</code> rendering as <code>true</code>, <code>false</code> in the admin interface. <a href="https://github.com/tomchristie/django-rest-framework/issues/3227">#3227</a>)</li>
<li>Fix for ListFields with single value in HTML form input. (<a href="https://github.com/tomchristie/django-rest-framework/issues/3238">#3238</a>)</li>
<li>Allow <code>request.FILES</code> for compat with Django's <code>HTTPRequest</code> class. (<a href="https://github.com/tomchristie/django-rest-framework/issues/3239">#3239</a>)</li>
</ul>
<h3 id="320">3.2.0</h3> <h3 id="320">3.2.0</h3>
<p><strong>Date</strong>: <a href="https://github.com/tomchristie/django-rest-framework/issues?q=milestone%3A%223.2.0+Release%22">6th August 2015</a>.</p> <p><strong>Date</strong>: <a href="https://github.com/tomchristie/django-rest-framework/issues?q=milestone%3A%223.2.0+Release%22">6th August 2015</a>.</p>
<ul> <ul>
...@@ -595,6 +603,8 @@ ...@@ -595,6 +603,8 @@
<!-- 3.1.3 --></p> <!-- 3.1.3 --></p>
<!-- 3.2.0 --> <!-- 3.2.0 -->
<!-- 3.2.1 -->
</div> <!--/span--> </div> <!--/span-->
</div> <!--/row--> </div> <!--/row-->
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment