Community
Participate
Working Groups
Build Identifier: The content assist within the editor doesn't attempt to either hide private methods or mark them as being private. Static methods and constructor methods are clearly indicated however, both within content assist and when you drill down into a class in the project explorer. IMO, private methods should be marked as being private when viewed from the project explorer, but should be hidden within content assist (unless they are being used locally in which case they should be marked as being private again). Reproducible: Always
JavaScript doesn't have a built-in notion of 'private', nor do we currently have a way to emulate that.
What about the JSDoc tag @private? Couldn't that be used to mark private members?
It's a design limitation at the moment. The modifiers are currently stored on the AST object, which limits the ability to represent a JS object with two properties pointing to the same function expression but with different modifiers.
