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 230128 - Go To Type should include suggestions if camel-case matches partly
Summary: Go To Type should include suggestions if camel-case matches partly
Status: NEW
Alias: None
Product: utilities
Classification: Unclassified
Component: Jump To (show other bugs)
Version: 7.3.1
Hardware: PC Linux
: P3 normal with 4 votes (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-22 15:40 UTC by everflux
Modified: 2015-03-03 16:53 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description everflux 2013-05-22 15:40:11 UTC
I would really like to not have to get the camel case exactly correct when I want to open a class.

Example:

CustomeWebApplicationInitializerImpl can currently only be accessed with CWA
I would like to see it with
CII (Custom...InitializerImpl) and
WAI (...WebApplicationInitializer...) and
CAI (Custom...ApplicationInitializer...)

If people don't like it (I can't imagine why...) it could be made configurable and/or only be triggered in case the regular exact camel case does not match for types in the currently open projects (not taking the JDK / library classes into account).
Comment 1 Tomas Zezula 2013-05-23 11:34:24 UTC
Will require configuration in options as described because it may significantly increate the amount of found types.
Comment 2 everflux 2013-05-23 12:02:17 UTC
Using partials should allow to restrict the results nicely.

For example
CWImpl (Custom...ApplicationInitializer...Impl)

This would help tremendously for tests as well:

MCTest (MasterCalculation...{whatever|foo|bar}...Test)

and voila I see all test classes for my business layer.

Perhaps "simply" adding wildcards could help here:

MCTest -> *M*C*Test*