Currently, options are part of the Models classes, residing within the static methods and being called out within the templates code.
That has to change, as on some occasions these are used within other contexts and that created unneeded Model class loading (mostly creates a rather messy codebase).
Using services that are instantiated as needed should be a better solution. Having general Interface and probably a base class would also prove to be useful.
There is a need to fully remove any calls to these methods from the templates (one place that uses it globally for language choice could stay). These should be passed to the templates from the Controller side instead. That approach should serve as a good enough separation on concerns.
Currently, options are part of the Models classes, residing within the static methods and being called out within the templates code.
That has to change, as on some occasions these are used within other contexts and that created unneeded Model class loading (mostly creates a rather messy codebase).
Using services that are instantiated as needed should be a better solution. Having general Interface and probably a base class would also prove to be useful.
There is a need to fully remove any calls to these methods from the templates (one place that uses it globally for language choice could stay). These should be passed to the templates from the Controller side instead. That approach should serve as a good enough separation on concerns.