mirror of
https://github.com/encode/django-rest-framework.git
synced 2025-01-24 00:04:16 +03:00
Fixed typos in tutorial
This commit is contained in:
parent
246a376dcf
commit
70b8e5b759
|
@ -204,7 +204,7 @@ We can also serialize querysets instead of model instances. To do so we simply
|
|||
|
||||
## Using ModelSerializers
|
||||
|
||||
Our `SnippetSerializer` class is replicating a lot of information that's also contained in the `Snippet` model. It would be nice if we could keep out code a bit more concise.
|
||||
Our `SnippetSerializer` class is replicating a lot of information that's also contained in the `Snippet` model. It would be nice if we could keep our code a bit more concise.
|
||||
|
||||
In the same way that Django provides both `Form` classes and `ModelForm` classes, REST framework includes both `Serializer` classes, and `ModelSerializer` classes.
|
||||
|
||||
|
|
|
@ -143,7 +143,7 @@ Once you've created a few code snippets, navigate to the '/users/' endpoint, and
|
|||
|
||||
## Object level permissions
|
||||
|
||||
Really we'd like all code snippets to be visible to anyone, but also make sure that only the user that created a code snippet is able update or delete it.
|
||||
Really we'd like all code snippets to be visible to anyone, but also make sure that only the user that created a code snippet is able to update or delete it.
|
||||
|
||||
To do that we're going to need to create a custom permission.
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user