Open yinonov opened 4 years ago
description of the current flow plan:
[ ] as sessions list is a common component we use in teacher's page as well and sessions link, commonly, to a session page in sessions path.
[ ] in session page if session belongs to user than it will be editable on that page itself.
[ ] create session anywhere on the site, and also in teacher, opens a routed popup (same as login) of session form component.
[ ] the form contains name, description & type fields and a show all fields button that expands a panel (expansion panel) with other important but optional fields.
[ ] once form is submitted user navigates to session page in sessions module where session can be edited on the spot
[ ] changes made to session will be kept as draft until "published"
Is your feature request related to a problem? Please describe. As session creation form conditionally changes its fields, it is best that it will be dependent on classical inheritance.
Describe the solution you'd like It's possible to create a base common form with extend groups which can be set by component.
Describe alternatives you've considered A clean alternative would be to use template driven forms as there would be only template source to build out the form value.
Additional context Keep in mind the typescript model extenders