-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TraceExplorer: getting the correct node to focus when node is part of a lambda expression #2468
Comments
…apping-for-Lambdas TraceExplorer: add interface for retrieving mapped nodes (#2468)
|
…sReadAccessForNodeMapping TraceExplorer: fix missing read access for node mapper (#2468)
…sReadAccessForNodeMapping TraceExplorer: weakens too restricted interface again (#2468)
…sReadAccessForNodeMapping TraceExplorer: Fixed NPE (#2468)
Another problem is, that a trace record stores the nodes but the interface only allows to get the Reference of it within the model. This of cause may result in returning null because in case of a lambda expression the traced node is only a copy of the original without a model. This can be resolved by introducing the required method to the interface ITraceRecord returning the node instead of the node reference. |
…sReadAccessForNodeMapping TraceExplorer: Extended ITraceRecord interface and fixed method (#2468)
Also see:
IETS3/iets3.opensource#1032
The text was updated successfully, but these errors were encountered: