Fix bug in code lens preference listener

Wrong keys were being used for disabling specific code minings.
Thus the code minings did not actually get disabled as/when intended.
This commit is contained in:
Kris De Volder
2018-12-18 11:41:25 -08:00
parent 8851937f79
commit d89baf2146

View File

@@ -65,12 +65,12 @@ public class BootLanguageServerPreferencesPage extends FieldEditorPreferencePage
jdtPrefs.putBoolean("editor_codemining_enabled", true);
//Disable all individual code minings. Since code mining wasn't enabled before...
//This merely serves to ensure they don't start showing up all of a sudden.
jdtPrefs.putBoolean("org.eclipse.jdt.ui/java.codemining.references", false);
jdtPrefs.putBoolean("org.eclipse.jdt.ui/java.codemining.references.onMethods", false);
jdtPrefs.putBoolean("org.eclipse.jdt.ui/java.codemining.references.onFields", false);
jdtPrefs.putBoolean("org.eclipse.jdt.ui/java.codemining.references.onTypes", false);
jdtPrefs.putBoolean("org.eclipse.jdt.ui/java.codemining.implementations", false);
jdtPrefs.putBoolean("org.eclipse.jdt.ui/java.codemining.atLeastOne", false);
jdtPrefs.putBoolean("java.codemining.references", false);
jdtPrefs.putBoolean("java.codemining.references.onMethods", false);
jdtPrefs.putBoolean("java.codemining.references.onFields", false);
jdtPrefs.putBoolean("java.codemining.references.onTypes", false);
jdtPrefs.putBoolean("java.codemining.implementations", false);
jdtPrefs.putBoolean("java.codemining.atLeastOne", false);
}
}
}