Eclipse Community Forums: TMF (Xtext) » Using FQN rule in reference rules does not work as expexcted.

Home » Modeling » TMF (Xtext) » Using FQN rule in reference rules does not work as expexcted.(Qualified name does not resolve)

Show: Today's Messages :: Show Polls :: Message Navigator

Using FQN rule in reference rules does not work as expexcted. [message #1837082]

Thu, 21 January 2021 17:54

Olaf Bigalk

Messages: 155
Registered: July 2009
Location: Berlin

Senior Member

I have the following parts in my grammar:

DynamicText:
	name=ID ":=" feature=[ecore::EStructuralFeature|QN] ("with" function=ID)
;
	
terminal QN:
	ID ('.' ID)+
;

the generated editor depicts that "DynamicText" could not be resolved.

var xxx := DynamicText.feature

I exspected " DynamicText.feature" gets parsed together as QN and then be compared to the scope provided here.

What is wrong ?

Report message to a moderator

Re: Using FQN rule in reference rules does not work as expexcted. [message #1837083 is a reply to message #1837082]

Thu, 21 January 2021 18:42

Christian Dietrich

Messages: 13768
Registered: July 2009

Senior Member

afaik estructural features are not in the index so it wont work with default scoping.
maybe you can try an eclass with QN + a separate reference for the feature.
or you do a reference to an epackage and do scoping for the qualified features manually.

also see open model element dialog

Attachment: Bildschirmfoto 2021-01-21 um 19.41.31.png
(Size: 118.04KB, Downloaded 12 times)
Attachment: Bildschirmfoto 2021-01-21 um 19.41.23.png
(Size: 88.14KB, Downloaded 11 times)

Need professional support for Xtext, Xpand, EMF?
Go to: https://www.itemis.com/en/it-services/methods-and-tools/xtext
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

Report message to a moderator

Re: Using FQN rule in reference rules does not work as expexcted. [message #1837089 is a reply to message #1837083]

Thu, 21 January 2021 22:19

Olaf Bigalk

Messages: 155
Registered: July 2009
Location: Berlin

Senior Member

Sorry, I didn't mentioned I have a custom ScopeProvider for this feature and that delivers exactly what you see "DynamicText.feature"
That is why I am wondering about this behavior

Report message to a moderator