Community
Participate
Working Groups
For newbies (like me), it would help to avoid stupid mistakes which have catastrophic impacts on run-time performance if a New Tree Element > Tree Item had a DEFAULT Semantic Candidate Expression of feature:eAllContents - just like a New Diagram Element > Sub Node Mapping already does.
Agreed on principle, we'll just have to be careful on how exactly we implement this to avoid changing the semantics of existing tree diagrams where the semanticCandidatesExpression is not set.
Just updating the ItemProvider would do the trick and avoid impacting all the .odesign which are already in the wild.
See https://git.eclipse.org/r/25346
Fixed by 93515a9c89a68fa6445dd2be81616791771ac1c0.
Available in Sirius 1.0.0M7 (see https://wiki.eclipse.org/Sirius/1.0.0M7 & http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/tag/?id=v1.0.0M7).