Files changed (2)
+You probably use one of these two ways for making a view that renders a form and then validates it on submit:
+These both work and they're fine but you often have to repeat yourself and you have to deal with ``if`` conditions when debugging. Not much fun, not very clean.
+Below that is the ``get()`` method that handles all ``GET`` requests. Typically it just takes ``self`` and ``request`` but if your route requires more arguments, they'll need to be specified here, too.
+And, surprise, surprise, below that is ``post()`` that takes care of your ``POST`` requests. Same arguments as ``get()`` since it has to be hit by the same route.
+True, we don't have ``@login_required`` on our methods and it won't work if you just add it there. What you can do, though, is wrap the ``dispatch()`` method and that will wrap all methods from that view with whatever
+If you really hate having to import each view, at the bottom of your ``views.py`` file, you can do something like: ``awesome_view = MyAwesomeView.as_view()`` and then set your URLs view as ``app.awesome_view``. I don't
+Thanks and I hope that helps everyone get a small grip on class-based views. There are many other class-based views available, such as ``FormView`` for handling form rendering and validation (so this entire method