diff options
Diffstat (limited to 'docs/topics/2.2-announcement.md')
| -rw-r--r-- | docs/topics/2.2-announcement.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/2.2-announcement.md b/docs/topics/2.2-announcement.md index d7164ce4..02cac129 100644 --- a/docs/topics/2.2-announcement.md +++ b/docs/topics/2.2-announcement.md @@ -75,7 +75,7 @@ This more explicit behavior on serializing and deserializing data [makes integra The implicit to-many behavior on serializers, and the `ManyRelatedField` style classes will continue to function, but will raise a `PendingDeprecationWarning`, which can be made visible using the `-Wd` flag. -**Note**: If you need to forcibly turn off the implict "`many=True` for `__iter__` objects" behavior, you can now do so by specifying `many=False`. This will become the default (instead of the current default of `None`) once the deprecation of the implicit behavior is finalised in version 2.4. +**Note**: If you need to forcibly turn off the implicit "`many=True` for `__iter__` objects" behavior, you can now do so by specifying `many=False`. This will become the default (instead of the current default of `None`) once the deprecation of the implicit behavior is finalised in version 2.4. ### Cleaner optional relationships @@ -103,9 +103,9 @@ The `blank` keyword argument will continue to function, but will raise a `Pendin ### Simpler object-level permissions -Custom permissions classes previously used the signatute `.has_permission(self, request, view, obj=None)`. This method would be called twice, firstly for the global permissions check, with the `obj` parameter set to `None`, and again for the object-level permissions check when appropriate, with the `obj` parameter set to the relevant model instance. +Custom permissions classes previously used the signature `.has_permission(self, request, view, obj=None)`. This method would be called twice, firstly for the global permissions check, with the `obj` parameter set to `None`, and again for the object-level permissions check when appropriate, with the `obj` parameter set to the relevant model instance. -The global permissions check and object-level permissions check are now seperated into two seperate methods, which gives a cleaner, more obvious API. +The global permissions check and object-level permissions check are now separated into two separate methods, which gives a cleaner, more obvious API. * Global permission checks now use the `.has_permission(self, request, view)` signature. * Object-level permission checks use a new method `.has_object_permission(self, request, view, obj)`. |