| Summary: | [content assist] <init> shows up as a completion proposal | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Philippe Marschall <philippe.marschall> | ||||
| Component: | General | Assignee: | Chris Jaun <cmjaun> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Nitin Dahyabhai <thatnitind> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cmjaun | ||||
| Version: | 3.3 | Flags: | thatnitind:
review+
|
||||
| Target Milestone: | 3.2.5 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 193724 [details]
patch
Removes the <init> proposal.
Only shows a constructor in content assist if used in a "new" expression.
Checked into 3.2.5 and HEAD. |
<init> the name of the Java constructor shows up as a completion proposal. Write the code below var x = {}; x. and trigger the completion proposals on x. <init> shows up as a function but shouldn't.