|
Re: X-Text Linking Services [message #1767011 is a reply to message #1766977] |
Thu, 29 June 2017 13:55   |
|
You would have to adjust your scope provider to provide these simple names instead of qualified names. Question is how you determine which namespace should be imported.
I suggest to read the scoping documentation carefully first and look at this presentation:
https://de.slideshare.net/holgerschill/deep-dive-into-xtext-scoping-local-and-global-scopes-explained
The most trivial solution to allow only simple names. This might work for your use case first, but in real projects there are just a few cases where this is a good idea. In this case bind the SimpleNameProvider as IQualifiedNameProvider
MyRuntimeModule:
override bindIQualifiedNameProvider() {
org.eclipse.xtext.naming.SimpleNameProvider
}
|
|
|
|
Re: X-Text Linking Services [message #1767021 is a reply to message #1767020] |
Thu, 29 June 2017 14:53  |
|
No and this does not make sense. If a name is ambiguous and you have to qualify it then you have to provide a qualified name. Using SimpleNameProvider is the wrong choice then.
Instead you will have to create a proper scope with the names of the class that is the context.
You will have to customize your scope provider.
|
|
|
Powered by
FUDForum. Page generated in 0.02990 seconds