Bug 414621 - Code complition for var's with type omitted in initialization lack type-specific operations
Summary: Code complition for var's with type omitted in initialization lack type-speci...
Status: NEW
Alias: None
Product: QVTo
Classification: Modeling
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-07 22:32 EDT by Alex Paperno CLA
Modified: 2013-08-18 13:45 EDT (History)
2 users (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 Alex Paperno CLA 2013-08-07 22:32:30 EDT 
To reproduce the problem, type the following:
----------
var aa="";
aa./* activate completion */
----------
The code complition list would lack all the String-specific operations, such as toLower(), indexOf() etc.

The problem is reproducible for other types as well (Integer, Real).
Comment 1 Christopher Gerking CLA 2013-08-11 06:38:45 EDT 
Since the variable is untyped, how should the code completion obtain any type-specific operations? The fact that there is a String bound to the variable is runtime information, thus not available when code completion is triggered.

Why not just specifying a type here?
Comment 2 Christopher Gerking CLA 2013-08-11 06:46:23 EDT 
Sorry, I was unaware of the fact the it is possible to derive the type from the initializer in OCL/QVTo. Consequently, your request is of course valid.
Comment 3 Sergey Boyko CLA 2013-08-18 13:45:45 EDT 
It's definitely an omission in completion engine. Should be fixed.