DRY entities #7

Merged

turtle merged 18 commits from feature/dry-entities into development

2024-01-13 00:49:26 +00:00

turtle commented

2024-01-11 01:21:25 +00:00

(Migrated from git.turtle-host.de)

Rewrite the whole resource / entity system so that it adheres to the DRY-principle (Right now, there is far too much boilerplate code).

One approach might be to use the interfaces in the API module to reverse-engineer data classes and database schemes. Though, this may cause some issues as it cannot accommodate any special cases.

Another approach could be a stricter definition of each resource in a YAML file that would be used as a template for data storage. This would allow for more fine-grained debugging and development, while requiring at least some boilerplate code, as entities would have to be defined in both YAML files and API interfaces (which would have to be kept in sync).

This starts as a draft as it is an experimental feature that will need some tests to be implemented in the first place.

Rewrite the whole resource / entity system so that it adheres to the DRY-principle (Right now, there is far too much boilerplate code). One approach might be to use the interfaces in the API module to reverse-engineer data classes and database schemes. Though, this may cause some issues as it cannot accommodate any special cases. Another approach could be a stricter definition of each resource in a YAML file that would be used as a template for data storage. This would allow for more fine-grained debugging and development, while requiring at least some boilerplate code, as entities would have to be defined in both YAML files and API interfaces (which would have to be kept in sync). This starts as a draft as it is an experimental feature that will need some tests to be implemented in the first place.