Skip to content

Commit 8a626cd

Browse files
committed
Stop hiding Activity Bar in ISE Mode
The user can, if they really wish, do this with `workbench.action.toggleActivityBarVisibility`, but at least in the latest Insiders it does not appear we can set this to `false` any more. Moreover, it's a confusing UI change to make even for the sake of an "ISE-like" experience. Simplest answer seems to be to stop trying to hide it so as to unblock our CI.
1 parent 5628cc6 commit 8a626cd

File tree

1 file changed

+0
-7
lines changed

1 file changed

+0
-7
lines changed

src/features/ISECompatibility.ts

-7
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
// Licensed under the MIT License.
33

44
import * as vscode from "vscode";
5-
import { getSettings } from "../settings";
65

76
interface ISetting {
87
path: string;
@@ -16,7 +15,6 @@ interface ISetting {
1615
export class ISECompatibilityFeature implements vscode.Disposable {
1716
// Marking settings as public so we can use it within the tests without needing to duplicate the list of settings.
1817
public static settings: ISetting[] = [
19-
{ path: "workbench.activityBar", name: "visible", value: false },
2018
{ path: "debug", name: "openDebug", value: "neverOpen" },
2119
{ path: "editor", name: "tabCompletion", value: "on" },
2220
{ path: "powershell.integratedConsole", name: "focusConsoleOnExecute", value: false },
@@ -65,11 +63,6 @@ export class ISECompatibilityFeature implements vscode.Disposable {
6563

6664
// Show the PowerShell view container which has the Command Explorer view
6765
await vscode.commands.executeCommand("workbench.view.extension.PowerShell");
68-
69-
if (!getSettings().sideBar.CommandExplorerVisibility) {
70-
// Hide the explorer if the setting says so.
71-
await vscode.commands.executeCommand("workbench.action.toggleSidebarVisibility");
72-
}
7366
}
7467

7568
private async DisableISEMode(): Promise<void> {

0 commit comments

Comments
 (0)