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
The cross-language consisteny of templates is currently not ensured, leading to low quality over time as features are implemented and not maintained over all languages immediately.
I suggest two ways to go:
a) Use centralized template snippets (mustache lambdas)
b) Ensure consistency by adding Unittests which will track snippets across all languages with opt-out decision. Opt-outs have to be explained in the unittest/template.
IMHO a) would be easier to do as we have only one place to maintain.
b) allows better tracking of changes and is maybe better by not forcing immediate updates cross-languages.
For version 3, the templating engine is now handlebar.
A lot of refactoring will be necessary to generate code with the new engine and with the new specification format as input.
I have the feeling with the current situation, that having a lot of copy paste code in the templates (between several java generators for example) will not make the task easy.
Activity
jmini commentedon Feb 23, 2018
For version 3, the templating engine is now handlebar.
A lot of refactoring will be necessary to generate code with the new engine and with the new specification format as input.
I have the feeling with the current situation, that having a lot of copy paste code in the templates (between several
javagenerators for example) will not make the task easy.