Problem with content assist and grammar fragments

[meysholdt]

For grammar

Model:
	foo+=(Works | Broken)*;

Works:
	"works" name=ID (ids+=ID ("." ids+=ID)* ";")* (refs+=[Works|ID] ("." refs+=[Works|ID])* "X" ";")*;

Broken:
	"broken" name=ID Fragment (refs+=[Broken|ID] ("." refs+=[Broken|ID])* "X" ";")*;

fragment Fragment *:
	(ids+=ID ("." ids+=ID)* ";")*;

with document

 works n x.x; n.n X;
 broken n x.x; n.n X;

The following problem occurs:
When triggering content assist at n.|n, I expect n to be proposed. This works fine for the first n.n, but for the second nothing is proposed.

The expectation is fulfilled when setting the parameter strict to false in ContentAssistContextFactory.java:213

[cdietrich]

similar grammar with problems

Model:
	DEFINE STREAM name=ID 		
;

fragment STREAM: ('stream');
fragment DEFINE: ('define' );

[szarnekow]

@cdietrich Your example grammar appears to be broken. The fragments should be defined as whildcards. Looks like a validation is missing for the grammar lang.

[cdietrich]

hi, what do you mean by

"defined as wildcards"

[szarnekow]

fragment STREAM: ('stream');
fragment DEFINE: ('define' );

is equivalent to

fragment STREAM returns EString: ('stream');
fragment DEFINE returns EString: ('define' );

thus these fragments are data type rules and we do not propose anything for DT rules.

fragment STREAM returns Model: ('stream'); // typed fragments can be used by rules where the 'current' is of type Model
fragment DEFINE returns Model: ('define' );

or

fragment STREAM *: ('stream'); // wildcard fragment can be used everywhere
fragment DEFINE *: ('define' );

turns those two rules into proper parser rule fragments.