-
-
Notifications
You must be signed in to change notification settings - Fork 34.2k
Closed
Labels
replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.
Description
Version
25.0.0
Platform
Subsystem
repl
What steps will reproduce the bug?
> class X { x = 1 }
undefined
> X.Y = class Y { y = 2 }
[class Y]
> new X. <[Tab]> <[Tab]>
new X.__proto__ new X.hasOwnProperty new X.isPrototypeOf new X.propertyIsEnumerable
new X.toLocaleString new X.toString new X.valueOf
new X.constructor
new X.xHow often does it reproduce? Is there a required condition?
What is the expected behavior? Why is that the expected behavior?
Property access has higher precedence than new, so this should autocomplete from the properties of X.
What do you see instead?
Autocompletion from the properties of new X(). If X is not a constructor, offers nothing.
Additional information
The fact that the completer also triggers side-effects from calling the constructor in question is less than ideal, but this isn't the first issue on that front.
Metadata
Metadata
Assignees
Labels
replIssues and PRs related to the REPL subsystem.Issues and PRs related to the REPL subsystem.