Adding django-versatileimagefield to DRF 3rd party docs #2917
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I might be missing something, but generally shouldn't this only go under one section? "Serializer fields" fits pretty well, but the others appear to be pushing it a bit. |
|
Hey @kevin-brown – I added it to the 'Misc' and 'Serializer fields' section after this back-and-forth with @tomchristie here: respondcreate/django-versatileimagefield#12 |
|
For some reason I was imagining a third one there (under "Views" for some reason), I probably looked at the diff too quickly. |
kevin-brown
added a commit
that referenced
this pull request
May 7, 2015
Adding django-versatileimagefield to DRF 3rd party docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes respondcreate/django-versatileimagefield#12