No description provided.
Fallback form creation to default form type if given purpose has no a…
…ssociated form type
I've thought again about the form type creator resolving rules and currently it follows this one:
I think it'll be better to follow this one:
@gquemener I think you should remove parent entities support altogether from rule or convention becomes too complex. Convention should be easy and simple to describe. And your "use parent type if no current type available" is easily achievable by creating simply empty type class, that extends parent.
We need to preserve balance between complexity of manual implementation and complexity of convention rules.
So, rule becomes simple: