|Re: Organise imports in my DSL [message #1062345 is a reply to message #1062339]
||Fri, 07 June 2013 10:13
| Jan Koehnlein
Registered: July 2009
That's of course your choice. The current implementation relies on the |
Xbase/Xtype and the JvmModel, i.e. on Java types (inferred or native).
Depends on your target if it's worthwhile to refactor.
A complete solution involves a lot of services, e.g. content assist
(proposing a type automatically adds an import), validation (find unused
imports), UI (a dialog for choosing from ambiguous candidates),
refactoring, quickfix etc. That's what makes it complicated.
Am 07.06.13 11:37, schrieb Alfredo Capozucca:
> Dear Jan,
> Thanks for the tip. Wouldn't you consider refactoring as a choice to
> implement this functionality?
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Get professional support from the Xtext committers at www.typefox.io
Powered by FUDForum
. Page generated in 0.02999 seconds