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

Bug 447471

Summary: Feature Name field should have the completion and validation at development time
Product: [Modeling] Sirius Reporter: Nikolay Manolov <nik.manolov>
Component: DiagramAssignee: Project Inbox <sirius.diagram-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: florian.barbin, laurent.fasani, pierre-charles.david
Version: unspecifiedKeywords: triaged
Target Milestone: ---   
Hardware: PC   
OS: Windows 8   
Whiteboard:

Description Nikolay Manolov CLA 2014-10-16 03:01:34 EDT 
Fields such as Reference Name in the New Instance creation tool should not be simple text fields, but be validated when text is entered. Those fields refer to class properties from the metamodel. 
A typo in such a field is detected at runtime, which is too late.
Suggestions for the field value would be ideal. They could be fetched from the metamodel.
Comment 1 Pierre-Charles David CLA 2014-10-16 05:54:33 EDT 
I'm not sure how hard to enforce this constraint, as there are use cases where the environment of the specifier and thus the metamodel installed at development time is not exactly the same as the one the end-user will have. We don't want to be too strict and forbid the opening of a VSM with hard references to a given version of a specific metamodel, or forbid the specifier to enter what looks like an error statically but may work perfectly fine in the runtime environment. And whatever we do in the VSM editor, we must keep the runtime checks (and improve the error message if needed).

However even with this in mind, we should at least provide a warning on VSM validation if we detect such a potential issue.
Comment 2 Laurent Fasani CLA 2015-07-15 03:48:13 EDT 
This ticket should also hold the completion capability for every feature field (reference and attribute) in the VSM. I'll change the title of this ticket consequently.
Comment 3 Florian Barbin CLA 2017-05-12 09:27:08 EDT 

*** This bug has been marked as a duplicate of bug 479049 ***