Bug 124280 - [assist] Content Assist in inner class offers Object methods twice
Summary: [assist] Content Assist in inner class offers Object methods twice
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 19892
  Show dependency tree
 
Reported: 2006-01-18 06:43 EST by Markus Keller CLA
Modified: 2022-07-27 05:55 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2006-01-18 06:43:48 EST
I20060117-0800

Content Assist in inner class offers Object methods twice. This doesn't make sense unless one of the proposals explicitly targets the outer class (e.g. "Try.this.getClass()") and indicates this in the label.

public class Try {
    private class Inner {
        public void run() {
            // content assist here
        }
    }
}
Comment 1 Tom Hofmann CLA 2006-01-18 09:15:45 EST
No regression - this is the case since at least eclipse 3.1.

Moving to jdt-core as I think that core should not be proposing hidden methods from the enclosing type without qualification.
Comment 2 Olivier Thomann CLA 2006-10-10 15:48:24 EDT
Reproduced with latest.
Comment 3 Dani Megert CLA 2009-09-21 06:40:01 EDT
The completions proposed by JDT Core are correct, see bug 19892. However, currently it is hard for us to deal with this: we would have to parse the completion string for .this. and figure out the receiver from that string.

JDT Core should provide us with the receiver information, e.g. by reusing CompletionProposal.getReceiverSignature() which got introduced in 3.4 or providing the information via new API. That information would be empty/null in the normal case and contain the receiver type for cases like the one described in this bug.
Comment 4 Eclipse Genie CLA 2020-07-02 02:51:58 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2022-07-27 05:55:23 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.