{"id":505,"date":"2013-07-21T21:05:32","date_gmt":"2013-07-22T01:05:32","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/acts\/?p=505"},"modified":"2013-07-21T21:05:32","modified_gmt":"2013-07-22T01:05:32","slug":"django-formsets-the-worst-thing-ever","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/acts\/2013\/07\/21\/django-formsets-the-worst-thing-ever\/","title":{"rendered":"Django Formsets, the worst thing ever?"},"content":{"rendered":"

This kind of thing really attracted me to django, but then the usability of it goes entirely out the window when you take a closer look.<\/p>\n

Formsets are basically a container for an arbitrary collection of forms. A form is a abstraction layer for UI, but I’ve seen they (or rather ModelForms) can be somewhat helpful as a funnel for POST vars and validation of the model. Maybe my issue is that the use I’ve found for them is not the primary concern people have.<\/p>\n

from https:\/\/docs.djangoproject.com\/en\/dev\/topics\/forms\/formsets\/<\/p>\n

\r\n>>> ArticleFormSet = formset_factory(ArticleForm, formset=BaseArticleFormSet)\r\n>>> data = {\r\n...     'form-TOTAL_FORMS': u'2',\r\n...     'form-INITIAL_FORMS': u'0',\r\n...     'form-MAX_NUM_FORMS': u'',\r\n...     'form-0-title': u'Test',\r\n...     'form-0-pub_date': u'1904-06-16',\r\n...     'form-1-title': u'Test',\r\n...     'form-1-pub_date': u'1912-06-23',\r\n... }\r\n>>> formset = ArticleFormSet(data)\r\n>>> formset.is_valid()\r\n<\/pre>\n
See, how you would expect something like this to work is it would take in a list, or at least a dict with a list. But no, they have you cat “form-n-” to the field name. This is just so sloppy I have to point it out.<\/p>\n
They spent so much time figuring out how to take away customizability from the front end, they weren’t paying attention to the backend.<\/p>\n","protected":false},"excerpt":{"rendered":"
This kind of thing really attracted me to django, but then the usability of it goes entirely out the window when you take a closer look. Formsets are basically a container for an arbitrary collection of forms. A form is a abstraction layer for UI, but I’ve seen they (or rather ModelForms) can be somewhat […]<\/p>\n","protected":false},"author":4571,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63924,64008],"tags":[111222,50627,64075,64076,64719,64074,64077,5464],"class_list":["post-505","post","type-post","status-publish","format-standard","hentry","category-atg","category-flashcards","tag-dict","tag-django","tag-form","tag-formset","tag-list","tag-model","tag-modelform","tag-python"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/505","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/users\/4571"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/comments?post=505"}],"version-history":[{"count":2,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/505\/revisions"}],"predecessor-version":[{"id":507,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/posts\/505\/revisions\/507"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/media?parent=505"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/categories?post=505"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/acts\/wp-json\/wp\/v2\/tags?post=505"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}