Add a setting to control whether 'textEdit' of completion items can be resolved (#3072)

* Add a setting to control whether 'textEdit' of completion item can be lazy-resolved

Signed-off-by: Sheng Chen <[email protected]>

Author: jdneo

README.md

@@ -218,14 +218,17 @@ The following settings are supported:
   - auto
   - on
   - off
-* `java.sharedIndexes.location`: Specifies a common index location for all workspaces. See default values as follows:  
+* `java.sharedIndexes.location`: Specifies a common index location for all workspaces. See default values as follows:
   - Windows: First use `"$APPDATA\\.jdt\\index"`, or `"~\\.jdt\\index"` if it does not exist
   - macOS: `"~/Library/Caches/.jdt/index"`
   - Linux: First use `"$XDG_CACHE_HOME/.jdt/index"`, or `"~/.cache/.jdt/index"` if it does not exist
 * `java.refactoring.extract.interface.replace`: Specify whether to replace all the occurrences of the subtype with the new extracted interface. Defaults to `true`.
 * `java.import.maven.disableTestClasspathFlag` : Enable/disable test classpath segregation. When enabled, this permits the usage of test resources within a Maven project as dependencies within the compile scope of other projects. Defaults to `false`.
 * `java.configuration.maven.defaultMojoExecutionAction` : Specifies default mojo execution action when no associated metadata can be detected. Defaults to `ignore`.
 
+New in 1.18.0
+* `java.completion.lazyResolveTextEdit.enabled`: [Experimental] Enable/disable lazily resolving text edits for code completion. Defaults to `true`.
+
 Semantic Highlighting
 ===============
 [Semantic Highlighting](https://github.com/redhat-developer/vscode-java/wiki/Semantic-Highlighting) fixes numerous syntax highlighting issues with the default Java Textmate grammar. However, you might experience a few minor issues, particularly a delay when it kicks in, as it needs to be computed by the Java Language server, when opening a new file or when typing. Semantic highlighting can be disabled for all languages using the `editor.semanticHighlighting.enabled` setting, or for Java only using [language-specific editor settings](https://code.visualstudio.com/docs/getstarted/settings#_languagespecific-editor-settings).

package.json

@@ -617,6 +617,12 @@
           "markdownDescription": "Specify whether to match case for code completion.",
           "scope": "window"
         },
+        "java.completion.lazyResolveTextEdit.enabled": {
+          "type": "boolean",
+          "default": true,
+          "description": "[Experimental] Enable/disable lazily resolving text edits for code completion.",
+          "scope": "window"
+        },
         "java.foldingRange.enabled": {
           "type": "boolean",
           "default": true,