This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 254910 - Go to type does not match correct match first
Summary: Go to type does not match correct match first
Status: RESOLVED DUPLICATE of bug 253389
Alias: None
Product: utilities
Classification: Unclassified
Component: Jump To (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-01 14:17 UTC by markiewb
Modified: 2015-09-08 15:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Shows the issue (713.34 KB, image/png)
2015-09-01 14:17 UTC, markiewb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description markiewb 2015-09-01 14:17:18 UTC
Created attachment 155805 [details]
Shows the issue

See screenshot

Case A)
ACTUAL 
"HibernateMDRepo" matches [Hibernate][M]aster[D]ataDefaultTimeSeries[Repo]sitory 

EXPECTED 
"HibernateMDRepo" matches better match [Hibernate][M]aster[D]ata[Repo]sitory

Case B)
ACTUAL 
"HibernateMasterDataRepo" matches [HibernateMasterData]DefaultTimeSeries[Repo]sitory 

EXPECTED 
"HibernateMDRepo" matches better match [HibernateMasterDataRepo]sitory

The new highlighting makes this error more obvious.

Product Version: NetBeans IDE Dev (Build 201509010002)
Updates: Updates available
Java: 1.8.0_20; Java HotSpot(TM) 64-Bit Server VM 25.20-b23
Runtime: Java(TM) SE Runtime Environment 1.8.0_20-b26
System: Windows 7 version 6.1 running on amd64; Cp1252; de_DE (nb
Comment 1 Tomas Zezula 2015-09-08 15:22:58 UTC
The hits are ordered by alphabets (historically from the beginning of the NetBeans).
If we want to change it, in the issue #253389 I propose to use Levenshtein distance for it, we need to add some switch for those who prefer lexicographic order.

For the NB 8.1 I can at least try to prefer exact match as Vladimir suggested, but it's  non trivial due to result filtering.

*** This bug has been marked as a duplicate of bug 253389 ***