Two Scoops Study Session 6

Based on chapters 8-9 of Two Scoops of Django, we looked at the criteria for using Function-Based Views (FBV) versus Class-Based Views (CBV). Either can work, but FBVs may be more suitable in cases where complexity increases or for simple cases like custom error views.

URLConf and view logic should be loosely coupled to improve reusability and extensibility. When URLs and views are tightly coupled, repetitive work increases and constraints arise for inheritance and extension, so namespaces should be used appropriately and directly pointing to views by string should be avoided.

Views should contain only the minimum needed for HTTP handling, while the rest of the business logic should be moved into model methods, manager methods, or utility functions. At its core, a Django view is a function that takes an HttpRequest and returns an HttpResponse, and CBVs ultimately fulfill the same role through View.as_view().

We also covered using locals() as context as an anti-pattern that makes maintenance difficult. Since even a variable name change can alter the rendering result, it's safer to explicitly pass the needed values to render().

In chapter 9, we covered using decorators as a way to leverage the strengths of FBVs. Decorators are useful for processing the request or post-processing the HttpResponse, but stacking too many makes the code hard to read, so their number should be limited.

In the deep-dive session, we organized the forms of views currently used in Django, and revisited the differences between URL / URI / URN and the Explicit is better than implicit principle. We then extended our understanding from a practical perspective by exploring how decorators are actually applied and how they are used in workplace settings.