You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some classes where we use the templates just to copy code, without modifications (except the package) and we have the VaadinatorUtils maven module where we only have the AbstractPlainJpa class.
Should we not move the static stuff also into this module? This would make it easier to split up a project into sub-modules which all use the same infrastructure artifacts.
The text was updated successfully, but these errors were encountered:
There's times where you need the package (like widgetset compilation). So far, those templates w/ only seem like KISS - providing an overall simple codebase (widgetset def, base presenter, ...). Or can you point to an example where it's really unnec? Still open for suggestions though...
We have some classes where we use the templates just to copy code, without modifications (except the package) and we have the
VaadinatorUtils
maven module where we only have theAbstractPlainJpa
class.Should we not move the static stuff also into this module? This would make it easier to split up a project into sub-modules which all use the same infrastructure artifacts.
The text was updated successfully, but these errors were encountered: