Formsets on the client-side #31

insin opened this Issue Mar 2, 2014 · 3 comments


None yet

1 participant

insin commented Mar 2, 2014


  • API designed around state never changing (i.e. a HTTP request being handled)
  • The management form is meaningless if you're never doing a standard form submission.
  • Do we really need one Form instance for every displayed form if there's no per-form customisation happening? What if each form's mutable state lived in the FormSet?
  • No API for adding/removing forms - just manually tweaking the variables and forcing React to update.
@insin insin modified the milestone: 0,7.0, 0.7.0 Mar 2, 2014
insin commented Mar 11, 2014

Implemented setState and removed the need to render or use a management form in 0.5.0

@insin insin added this to the 0.9 milestone Nov 6, 2014
insin commented Nov 6, 2014

Adding deleteForm, validate and some smaller items in 0.9 make formsets more usable on the client. Needs to be re-documented, though.

@insin insin removed this from the 0.9 milestone Nov 28, 2014
insin commented Dec 1, 2014

As of 0.9, formsets have the same mutable API as forms

@insin insin closed this Dec 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment