More control over completions (e.g., disable Java standard library method completions)

[Aminminminn]

I would like to request a feature to allow fine-grained control over completions in the extension. Specifically, I want to disable completions for Java standard library methods (e.g., String.split(), System.out.println(), etc.) while keeping completions for my project's dependencies, such as Gradle plugins and custom libraries.

Currently, the java.completion.enabled setting disables all completions, which is not ideal for my workflow. I rely heavily on Gradle plugin completions, and the Java standard library methods cannot be used in my project.

[rgrunber]

Can you try java.completion.filteredTypes and let me know if that works for your needs ? By default it filters out the following :

[ "java.awt.*", "com.sun.*", "sun.*", "jdk.*", "org.graalvm.*", "io.micrometer.shaded.*" ]

I guess you would want to add "java.*"

[Aminminminn]

Thanks for your answer but it doesn't work for my needs, this option only hides the classes but not their methods. I am trying to do something more brutal like removing completely the JDK (or removing it from the classpath) but putting an empty JDK in the options is not working..

[rgrunber]

Right. Ok, then it's a feature we need to implement. Either expanding filterTypes to also handle method and other kinds of completions or creating a separate filterMethods setting.

[rgrunber]

@Aminminminn , what should happen if you've chosen to filter a type, or an entire package (with wildcards), but a source file has an import statement to some type covered by the filter. Should any completion involving that type and its methods continue to be excluded, or should the user's choice to explicitly import that type overrie/cancel the filter as long as the import exists in the file ?

The example you have above includes things from java.lang which wouldn't need an explicit import, so it wouldn't run into this case.

[Aminminminn]

Sorry for the really really late answer, I think its methods should not be excluded if the import is explicitly importing them. But it is a rare case that I don't think I will encounter using this.