Incomplete namespace (path string) in cross-reference

[Wilson008]

We have two approaches for cross-referencing type and prototype:

• for type references (e.g., from FunctionFlowPort to EADatatype or from DesignFunctionPrototype to DesignFunctionType), the type can be selected. However, it cannot be distinguished between equally named types in different namespaces. In the formatting part of Xtext, it should be possible to add the fully qualified namespace.
• call the namespace with full path, however there is an issue: For example, the referenced namespace should look like: "Struture.DesignPkg.FcnDesignPkg.WiperCtrlBasic.WiperParkStatus" it could give us the correct and full path string to user, but when user presses enter key, it only would input like this: "FcnDesignPkg.WiperCtrlBasic.WiperParkStatus", which then would cause error and is not what users want, so user has to input "Struture.DesignPkg." manually.

We should unify these approaches, that is,

1. select the most promising one
2. fix the corresponding issues
3. transfer the usages of the other approach to the fixed one

[joerg-holtmann]

We use approach number one, where we adapt the scope provider to compute the fully qualified name of the particular elements to be cross-referenced. The default scope provider has an issue with our language for computing the two topmost hierarchy levels.

See also https://www.eclipse.org/forums/index.php/t/1074040/ for injecting an instance of our adapted EastAdlQualifiedShortnameProvider to call the non-static function getFullyQualifiedName(EObject) of its super class.