| Summary: | Nameprovider cannot access references | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Christian Dietrich <christian.dietrich.opensource> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sebastian.zarnekow |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Christian Dietrich
We won't remove this assertion since it reveals actual bugs (like relying on cross references to compute a name). so that is the intended way to workarround this? using NodeModelUtils to read the Xtext? (In reply to comment #2) > so that is the intended way to workarround this? > > using NodeModelUtils to read the Xtext? That would be only a partial solution since the resolved entity may have a longer qualified name due to imports etc. but it may work in some cases. Another option would be to customize the scoping for instances of 'Usage' to make sure that their qualified name is computed locally. |