Proposal: Spread the Settings to make them visible in the settings panel

[JulianG]

The settings panel could look like this:

If instead of an array, we had 3 separate configuration properties:

    "configuration": {
      "properties": {
        "peacock.affectTitleBar": {
          "type": "boolean",
          "default": true,
          "description": "Specifies whether Peacock should affect the title bar."
        },
        "peacock.affectActivityBar": {
          "type": "boolean",
          "default": false,
          "description": "Specifies whether Peacock should affect the activity bar."
        },
        "peacock.affectStatusBar": {
          "type": "boolean",
          "default": false,
          "description": "Specifies whether Peacock should affect the status bar."
        }
      }
    }

[mikeerickson]

@JulianG @johnpapa Hey gang, if this change is made, please let me know as I am working on the CLI version and read these settings accordingly.

[johnpapa]

Neat idea. It seems no less hard coded than what exists today (meaning the extension only supports these already).

I like this because it uses the conventional settings UI and not a new command/menu.

Anyone else have an opinion?

[mikeerickson]

I like the direction, surely much clearer for the end user AND it promotes using the cool vscode setting UI

[johnpapa]

implemented in v.0.5.0

[JulianG]

awesome! I'll update asap!