Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 430579

Summary:	feature:eAllContents by default for Tree, like for diagram
Product:	[Modeling] Sirius	Reporter:	Michael Vorburger <mike>
Component:	Tree	Assignee:	Pierre-Charles David <pierre-charles.david>
Status:	CLOSED FIXED	QA Contact:	Maxime Porhel <maxime.porhel>
Severity:	normal
Priority:	P3	CC:	cedric.brun, florian.barbin, maxime.porhel, pierre-charles.david
Version:	1.0.0M7	Keywords:	triaged
Target Milestone:	1.0.0M7
Hardware:	PC
OS:	Linux
Whiteboard:

Description Michael Vorburger

2014-03-18 01:47:59 EDT

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.

Comment 1 Pierre-Charles David

2014-04-14 04:22:05 EDT

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.

Comment 2 Cedric Brun

2014-04-14 04:35:37 EDT

Just updating the ItemProvider would do the trick and avoid impacting all the .odesign which are already in the wild.

Comment 3 Pierre-Charles David

2014-04-22 08:50:44 EDT

See https://git.eclipse.org/r/25346

Comment 4 Pierre-Charles David

2014-04-25 10:43:23 EDT

Fixed by 93515a9c89a68fa6445dd2be81616791771ac1c0.

Comment 5 Pierre-Charles David

2014-05-12 03:45:40 EDT

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).