This is a fix for https://github.com/oursky/django-material-demo/pull/31. Turns out things are not that complicated. We just need to assign the parent instance back, which is something I expect the library to do. I think it might be because of the different behaviour of newer django version.
I think in the long run, we will need to maintain the django-superform ourselves, and we would not require developers to fix the behaviour like we do in this PR.
refs #7
This is a fix for https://github.com/oursky/django-material-demo/pull/31. Turns out things are not that complicated. We just need to assign the parent instance back, which is something I expect the library to do. I think it might be because of the different behaviour of newer django version.
I think in the long run, we will need to maintain the django-superform ourselves, and we would not require developers to fix the behaviour like we do in this PR.