Feature #2464
Updated by Alexander Watzinger 6 months ago
Currently we have a mixed bag of used classes at entity level, forms and displays that are not directly connected.
After some talks with colleagues and very helpful input from @Katharina, Lukas and Birger just to name a few I found a new approach:
Using one model config file which contains all information to build views, forms and similar in a generic way which would also have other advantages like:
* Easier model adaptions at one place
* Possibility to test for "allowed" relations
* More consistent layout, e.g. table headers, form fields order, ...
* Less error prone and fewer tests are needed
*Update*
Work has started in the *feature/new_classes* branch but will take some time.