@@ -458,17 +458,17 @@ public void apply(CompletionItem completion) throws Exception {
458
458
String replaceWith = edit .getLeft ().getNewText ();
459
459
int cursorReplaceOffset = 0 ;
460
460
461
- if (!Boolean .getBoolean ("lsp.completions.indentation.enable" )) {
462
- //Apply indentfix, this is magic vscode seems to apply to edits returned by language server. So our harness has to
463
- // mimick that behavior. See https://github.com/Microsoft/language-server-protocol/issues/83
464
- int referenceLine = edit .getLeft ().getRange ().getStart ().getLine ();
465
- int cursorOffset = edit .getLeft ().getRange ().getStart ().getCharacter ();
466
- String referenceIndent = doc .getLineIndentString (referenceLine );
467
- if (cursorOffset <referenceIndent .length ()) {
468
- referenceIndent = referenceIndent .substring (0 , cursorOffset );
469
- }
470
- replaceWith = replaceWith .replaceAll ("\\ n" , "\n " +referenceIndent );
471
- }
461
+ // if (!Boolean.getBoolean("lsp.completions.indentation.enable")) {
462
+ // //Apply indentfix, this is magic vscode seems to apply to edits returned by language server. So our harness has to
463
+ // // mimick that behavior. See https://github.com/Microsoft/language-server-protocol/issues/83
464
+ // int referenceLine = edit.getLeft().getRange().getStart().getLine();
465
+ // int cursorOffset = edit.getLeft().getRange().getStart().getCharacter();
466
+ // String referenceIndent = doc.getLineIndentString(referenceLine);
467
+ // if (cursorOffset<referenceIndent.length()) {
468
+ // referenceIndent = referenceIndent.substring(0, cursorOffset);
469
+ // }
470
+ // replaceWith = replaceWith.replaceAll("\\n", "\n"+referenceIndent);
471
+ // }
472
472
473
473
// Replace the cursor string
474
474
cursorReplaceOffset = replaceWith .indexOf (VS_CODE_CURSOR_MARKER );
0 commit comments