Bug 553100 - [Xtext][API] we must be able to save invalid string directly in the edited field when it is a string field
Summary: [Xtext][API] we must be able to save invalid string directly in the edited fi...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Others (show other bugs)
Version: 4.5.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 4.6.0   Edit
Assignee: Vincent Lorenzo CLA
QA Contact:
URL:
Whiteboard: S19
Keywords: api
Depends on:
Blocks:
 
Reported: 2019-11-15 07:34 EST by Vincent Lorenzo CLA
Modified: 2019-11-26 15:08 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vincent Lorenzo CLA 2019-11-15 07:34:52 EST 
Currently, when the user enters an invalid String, this string is saved into a stereotyped comment. 
This behavior is useful, when the string represents UML element (type, visibility, ... ), because in this case, we can set the invalid value in the target features. 

There is case where the entered string must be set in the feature (like OpaqueBehavior#body for example). 
In this case, we must be able to save the invalid string in the targeted feature. 

In order to do that, I propose to open the API provided by org.eclipse.papyrus.uml.xtext.integration.DefaultXtextDirectEditorConfiguration and by the implemented IParser.
Comment 1 Eclipse Genie CLA 2019-11-15 08:39:22 EST 
New Gerrit change created: https://git.eclipse.org/r/152730