redhat-developer / redhat-developer/vscode-java

Intellisense breaks for JDK types when certain (scala) libs are on the classpath

Open
#3,690 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

When triggering autocomplete (ctrl+space) targeting JDK type java.lang.reflect.Field or java.util.List and certain (scala) libs are on the classpath, expected suggestions are not coming.

I've observed that List and Function are broken by the scala lib itself and Field is broken by Akka HTTP

Environment
  • Operating System: Windows
  • JDK version: 21.0.3 (Adoptium)
  • Visual Studio Code version: 1.90.2
  • Java extension version: 1.32.1
Steps To Reproduce
  1. Attempt auto complete on variable type

Reproducer with dev container: https://github.com/spangaer/vscode-javals-completion-issue
(Dev container because SBT generated eclipse files, but my guess is that doesn't matter)

Current Result

image
image

Expected Result

image
image

Additional info

It looks to be really specific to the code completions. e.g creating a local var using Quick Fix... type inference does find the JDK types.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked dev-container reproducer and reproduce completion for java.lang.reflect.Field and java.util.List with the Scala and Akka HTTP libraries on the classpath. Compare completion behavior with and without those libraries; done means expected JDK type suggestions appear while Quick Fix type inference continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, scala, typescript
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.