Комментарии:
Hello. Nice video. Another way to use a certain serializer (InputSerializer) for all requests and a different one (OutputSerializer) for all responses is to override data property and many_init method of InputSerializer to use the OutputSerializer for responses and declare InputSerializer as the value of serializer_class attribute on your ModelViewset.
If anyone is interested I can write the code. Its a couple of lines
Why you are these days.. the last video is 1 year old
ОтветитьGreat video, by the way from today i am your subscriber)
I have some questions about django. (may be for your next vies, but i will be happy if you answer like at least shortly in comment:)))
1. what about action decorators, when you want to add different api (not crud)
2. what is best practice for using filterset classes?
3. best way for adding swagger (some problems when swagger do not read params of filter of genericviewsets filtersets when we use action decorators in it.
4. what is migrations file effective use, to not have conflicts, when you work 3-4 people on project?
5. orm, annotations, aggregations, rawsql which type is best for cases?
Very nicely explained man. keep up the good work
ОтветитьThis video is gold!
ОтветитьThis content is really good , thanks man
ОтветитьThank you man, cool and pretty clear
Ответить