-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix type completion when type name conflicts #2232
Conversation
When type completion are applied where the same simple name already imported in the scope, the second type completion is completed as a fully qualified completion.
Can one of the admins verify this patch? |
add to whitelist |
Yes in Eclipse when we have a Simple Name conflict, the fully qualified name is used as the completion text. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you @gayanper for your contribution!
You are welcome @jdneo |
- fix the performance downgrade introduced by eclipse-jdtls#2232. With that change, triggering completion via keyboard shortcut will take a long time. Now with the change, it will only do context sensitive import rewrite when resolving completion items. Signed-off-by: Sheng Chen <[email protected]>
…ems (#2453) * Only do context sensitive import rewrite when resolving completion items - fix the performance downgrade introduced by #2232. With that change, triggering completion via keyboard shortcut will take a long time. Now with the change, it will only do context sensitive import rewrite when resolving completion items. --------- Signed-off-by: sheche <[email protected]>
When type completion are applied where the same simple name already imported in the scope, the second type completion is completed as a fully qualified completion.