eclipse-jdt / eclipse-jdt/eclipse.jdt.ui

Content assist: subwords autocompletion improvement - match behavior of old Code recommenders

Open
#2,997 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
59
Forks
127
Avg merge
22h 47m
Merged PRs (30d)
28

Description

Hello, there was once Code recommenders project, that is now archived:
https://repo.eclipse.org/content/shadows/releases.unzip/org/eclipse/recommenders/stable/2.5.4/stable-2.5.4.zip-unzip/

It had a neat feature called subwords autocompletion:
![obrazek](https://github.com/eclipse-platform/eclipse.platform.ui/assets/135681/9c76692b-eb88-48e7-b922-c263d4b0773b)

I know eclipse has a setting for subword matches:
![obrazek](https://github.com/eclipse-platform/eclipse.platform.ui/assets/135681/290203d4-5539-4a6f-986b-03c960c66e01)
but it is lacking in how it searches in strings.

For example in searching with Code recommenders and typing
"Dbu.getrs" gives you:
![obrazek](https://github.com/eclipse-platform/eclipse.platform.ui/assets/135681/55d0490a-ed16-4080-89c1-85e0523ca67f)

While searching for the same text with Eclipse's standard content assist and subword matches turned on yields:
![obrazek](https://github.com/eclipse-platform/eclipse.platform.ui/assets/135681/843739b3-ff24-407e-bd7c-efcd040e3f41)

Code recommenders way of searching was superior to what is available now and **lets you navigate through type and method names much faster**. I'm still using old Code recommenders, but it is way outdated and may eventually stop working completely with new versions of Eclipse .

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.