Jérôme Lafréchoux

More on this. The use case presented in the tests above is a bit silly because you can't call `__init__` in `Document` template anyway. Also, I should be more explicit...

> From my point of view it's not such a big deal given a Document rotate around it data from the database and so should not initialize anything but them....

Another proposal with a `_super` method: ```python def test_super_in_inheritance(self): class Parent(Document): def _super(self, tmpl): return super(_get_impl_from_tmpl(self, tmpl)) def _get_impl_from_tmpl(self, tmpl): return self.opts.instance.retrieve_document(tmpl) class Meta: allow_inheritance = True name = fields.StrField()...

> I'm sure I can provide a failing test based on aa6f13c and the snippet above, but I'm not sure I can also provide a fix. Failing test would be...

I pushed a branch with a test for this: https://github.com/MongoEngine/flask-mongoengine/tree/listfield_validation

I guess it is not intentional. I also think one CSRF for the parent form would be nice.

@fmatray, still interested in this? Or should we close this issue?

I guess this is linked to https://github.com/MongoEngine/flask-mongoengine/issues/138#issuecomment-213485871. Can you please be more explicit?

The benefit would be you could write ``` form() form(obj=obj) ``` instead of ``` form(request.form) form(request.form, obj) ``` so you don't have to pass request.form explicitly. Is that it? Just...

Considering this a bug. I shall add a test and see if this can be solved.