xtext-core/org.eclipse.xtext.ide
Moritz Eysholdt 676736a4b8 [#16, contentAssist] add support for custom parser entry points
ContentAssist needs to use the entry point that can be obtained via 

NodeModelUtils.getEntryParserRule(INode) or 
XtextResource.getEntryPoint()

To support this, AbstractContentAssistParser does now implement 
IPartialEditingContentAssistParser, which is an interface that has been
introduced some time ago for the CodeTemplates language.

XtextAntlrGeneratorFragment2 will no longer generate getFollowElements()
for each language because that method is only able to invoke the first 
parser rule. Instead, there is now a gneric implementation in the super 
class.

Signed-off-by: Moritz Eysholdt <moritz.eysholdt@typefox.io>
2016-08-11 15:35:50 +02:00
..
.settings Removed old Gradle integration prefs 2016-07-07 11:22:13 +02:00
META-INF Moved projects to root of repository 2016-06-14 08:30:25 +02:00
src/org/eclipse/xtext/ide [#16, contentAssist] add support for custom parser entry points 2016-08-11 15:35:50 +02:00
xtend-gen/org/eclipse/xtext/ide [ls] Make sure that there is only one instance of BuildManager per 2016-07-29 15:37:07 +05:00
.classpath Checked in project metadata based on Buildship 2016-07-07 10:19:04 +02:00
.project Checked in project metadata based on Buildship 2016-07-07 10:19:04 +02:00
about.html Moved projects to root of repository 2016-06-14 08:30:25 +02:00
build.gradle Moved projects to root of repository 2016-06-14 08:30:25 +02:00