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
Currently CobiGen does not generate many import statements most of them are missing. This is somewhat compensated by invoking organize imports.
However, this solution is not sufficient and and reliable.
Sometimes the Classname itself is not unique and organize imports can not guess the import statement. So currently I often end up with code that can not compile and needs manual rework. This is not what we want to have.
Instead the templates should also iterate over the properties and add import statements. Still organize imports should be used to do tidy up of imports. For me the question is how to make it easy to generate the imports using macros and to avoid duplicated or pointless imports. Maybe we need to collect the imports in a set first and then generate the actual import statements.
Still for such things I think freemarker is a little limited and we need to open a door to embedding real code into macros for the required power but this is a different issue.
The text was updated successfully, but these errors were encountered:
Currently CobiGen does not generate many import statements most of them are missing. This is somewhat compensated by invoking organize imports.
However, this solution is not sufficient and and reliable.
Sometimes the Classname itself is not unique and organize imports can not guess the import statement. So currently I often end up with code that can not compile and needs manual rework. This is not what we want to have.
Instead the templates should also iterate over the properties and add import statements. Still organize imports should be used to do tidy up of imports. For me the question is how to make it easy to generate the imports using macros and to avoid duplicated or pointless imports. Maybe we need to collect the imports in a set first and then generate the actual import statements.
Still for such things I think freemarker is a little limited and we need to open a door to embedding real code into macros for the required power but this is a different issue.
The text was updated successfully, but these errors were encountered: