At the moment, etos does not generate the imports alongside a class / trait definition.
This is annoying, in particular when generating multiple packages with references from one to another.
The imports should be easily findable by checking :
- attributes' type,
- references' type,
- operations' return type,
- operations' attributes' return type.
At the moment, etos does not generate the imports alongside a class / trait definition.
This is annoying, in particular when generating multiple packages with references from one to another.
The imports should be easily findable by checking :