Feature #2464
Updated by Alexander Watzinger 7 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 A much better approach would be a connected and more generalized system (preferable with colleagues and very helpful composition). Talks about it have already began, e.g. with kind input from @Katharina, Lukas @Katharina and Birger just to name Lukas, but this would of course need a few I found a new approach: Using one model config file which contains all information while to build views, forms design, implement and similar in a generic way which would also have other advantages like: * Easier model adaptions at one place * Possibility to test so I put it on the next major version for "allowed" relations * Because it will be more generic it will be less error prone, needs viewer tests and similar now.