4 points by sebst 1 year, 1 month ago | 4 comments


 
2 points by bithive 1 year, 1 month ago | discuss | on: Django’s CBVs were a mistake
I started a new side project to get more into cbvs. They are really good if you have a lot of similar views. But for the heavy lifting you should use functional views. However cbvs are a great starting point
 
5 points by ehmatthes 1 year, 1 month ago | 1 comment | on: Django’s CBVs were a mistake
This should probably have a [2012] tag on the title. I haven't used CBVs enough to know which of these points are still valid, but I'd be much more interested in reading a more recent review. A lot has changed in the Python and Django world since 2012!
 
2 points by bithive 1 year, 1 month ago | discuss | parent | on: Django’s CBVs were a mistake
There is an update he wrote in 2015 on the same Article - his views remained the same. But then again just his opinion man
 
2 points by readevalprint 1 year, 1 month ago | discuss | on: Django’s CBVs were a mistake
I think the best of both worlds is possible with DRF's `extra_actions` You get a dedicated endpoint that uses the same permissions and queryset, but can easily make custom logic that doesn't fit in the whole class. [https://www.django-rest-framework.org/api-guide/viewsets/#marking-extra-actions-for-routing]