Draft: Add read only API with DRF #57
Closed
Conversation
This file contains 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
sveetch
changed the title
Closed
12 tasks
sveetch
added
New feature
… DRF viewset to implement publication lookup in api
…th authors and categories api test
…url namespace 'lotus-api'
…es are filter with article language
….get_categories()'
sveetch
force-pushed
the
try_drf_addition
branch
from
586b52c to
8daabdf
Compare
…r the full one) and with tests
…private' argument, finished author viewset tests
|
This branch has been squashed and delivered into new v0.7.0 https://github.com/emencia/django-blog-lotus/tree/v0.7.0 which will now continue the common release process, still have some things to see to include in this version before releasing. |
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.
This is currently experimental although it is correctly implemented, but it needs some works yet.
For now we only plan to make the API in read only. Write operation may comes further in another run since read operation are the first thing to ship.
At the end, every branch commits will be squashed into a single one, excepted for possible swagger implementation.