I have a schema with a base class, Organization. This base class has many fields and many relationships, too lengthy to reproduce here. Among them, an Organization has a many-to-many relationship with another class, Person (i.e. I have a person_organization table with isCrossRef: true ).
I have a child class, School, with a simple yaml schema that looks like this:
school:
is_public: boolean
_propel_behaviors:
concrete_inheritance:
extends: organization
When I generate the models, the BaseSchool class inherits from the Organization class, so I get the benefits of inherited methods, etc., and looks as if I will be able to use School methods to access related Persons. This looks as if it works nicely.
But the generated form, BaseSchoolForm, inherits from BaseFormPropel, and does not have the widget needed to populate the many-to-many Person relationship.
Is anyone working on this? To be clear, I'm not asking that the issue be addressed, I just want to know if I should dig in or if it's worth waiting for a fix that someone else is already working on. Many thanks.
I have a schema with a base class, Organization. This base class has many fields and many relationships, too lengthy to reproduce here. Among them, an Organization has a many-to-many relationship with another class, Person (i.e. I have a person_organization table with isCrossRef: true ).
I have a child class, School, with a simple yaml schema that looks like this:
school:
is_public: boolean
_propel_behaviors:
concrete_inheritance:
extends: organization
When I generate the models, the BaseSchool class inherits from the Organization class, so I get the benefits of inherited methods, etc., and looks as if I will be able to use School methods to access related Persons. This looks as if it works nicely.
But the generated form, BaseSchoolForm, inherits from BaseFormPropel, and does not have the widget needed to populate the many-to-many Person relationship.
Is anyone working on this? To be clear, I'm not asking that the issue be addressed, I just want to know if I should dig in or if it's worth waiting for a fix that someone else is already working on. Many thanks.