The current templating engine has multiple issues because it stayed pretty much untouched since it was introduced in the MVP created in under a day.
The appearant issues are:
Minified versions of the templates must be maintained separately
The way the templating language works is very static.
For example it wouldn't be possible to create one html file for each report or category.
The templates include crystal code directly compiled into the binary.
While this makes the templates very dynamic,
it makes template changes require re-compilations,
makes templates harder to debug and moves arbitrary logic outside of the main code.
To fix these issues, a makeover of the template engine should be done.
The current templating engine has multiple issues because it stayed pretty much untouched since it was introduced in the MVP created in under a day.
The appearant issues are:
Minified versions of the templates must be maintained separately
The way the templating language works is very static.
For example it wouldn't be possible to create one html file for each report or category.
The templates include crystal code directly compiled into the binary.
While this makes the templates very dynamic, it makes template changes require re-compilations, makes templates harder to debug and moves arbitrary logic outside of the main code.
To fix these issues, a makeover of the template engine should be done.