That is awesome! I found myself implementing this kind of functionality quite often. But the I find two use cases that don't seem to be covered:

  • having multiple forms of the same type (eg. updating two unrelated records at the same)
  • giving extra kwargs to the forms. (each form might get other kwargs).
5
pred4tor07•

Cool stuff! My approach to handling this problem in the past was using Ajax (or Intercooler.js) to submit the forms to separate endpoints for each.

1
Nick4753•

This is cool! I've used the same snippet of code I found on some forum years ago every time I need to do this but it isn't nearly as clean as this.

Support for multi-form class based views really should be in django core.

1
Nimor111•

The use case of User/Profile models is really well complimented in this library. It's kind of annoying to have to cut the data coming from a form in half in the service to write it separately in two different models. Great job!

1