|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Duplicate
|
|
This issue duplicates:
|
|
IDEADEV-8282
Detect Bindows-specific idiom
|
|
|
|
|
|
|
|
Problem with code completion in Bindows. In Bindows we use this construct: _p._myVariable = 1; _p._myFunction = function() {} The extra _ in the beginning of a variable name denotes a private class member. When invoking code completion in some other class, like so: this. every property and function in all of Bindows with _p is listed. properties of completely alien classes are listed... Is there anyway you can do something about this?
|
|
Description
|
Problem with code completion in Bindows. In Bindows we use this construct: _p._myVariable = 1; _p._myFunction = function() {} The extra _ in the beginning of a variable name denotes a private class member. When invoking code completion in some other class, like so: this. every property and function in all of Bindows with _p is listed. properties of completely alien classes are listed... Is there anyway you can do something about this? |
Show » |
|
New Feature
This issue (8283) has been marked as a duplicate of (8282), and that is partly correct. I don't know if Maxim fixed the private member part of it but here comes a clarification anyway:
In JavaScript there is no such thing as a private member but in Bindows there is. It is a convention that we enforce throughout the whole of bindows and it looks like this:
_p._myPrivateVariable;
_p._myPrivateFunction = function() {};
_p.myPublicVariable;
_p._myPublicFunction = function() {};
Private members of a superclass should not be listed in code completion.
(It would be nice however to turn this feature on/off)