Bug 250190 - codeSelect could be smarter
Summary: codeSelect could be smarter
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-08 17:21 EDT by Benjamin Muskalla CLA
Modified: 2022-08-02 09:20 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Muskalla CLA 2008-10-08 17:21:19 EDT
N20081005-2000

Take the following snippet:
---------------------------------
package p1;

public class A {
	public static void main(String[] args) {
		System.out.println("/some/path/image.bmp");
	}
}

/**
 * not intended
 */
class bmp {
}
---------------------------------

If you hover over bmp inside the string javadoc view and javadoc hover will show "not intended". I see the point that strings can contain class names but in this case it' just annoying. One way I could imagine is to only match if the string contains a full qualified name.
Comment 1 Dani Megert CLA 2008-10-09 03:13:38 EDT
codeSelect could be smarter and if the string in front of the '.' doesn't match the package name then don't return the type.

Other scenario:

/**
 * This should show a hover: HashMap and this is not: .HashMap
 */
Comment 2 Jerome Lanneluc CLA 2008-10-17 07:05:26 EDT
(In reply to comment #1)
> codeSelect could be smarter and if the string in front of the '.' doesn't match
> the package name then don't return the type.

In this case, the following scenario would still show "not intended":

package image;

public class A {
        public static void main(String[] args) {
                System.out.println("/some/path/image.bmp");
        }
}

/**
 * not intended
 */
class bmp {
}
Comment 3 Eclipse Genie CLA 2020-08-04 15:05:37 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 4 Eclipse Genie CLA 2022-08-02 09:20:06 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.