API shell text does not apply to Windows

Describe the bug When failing to connect to the daemon, the webui shows shell prompts that are invalid on Windows.

---

ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '["http://127.0.0.1:8080", "http://127.0.0.1:5001", "https://webui.ipfs.io"]' returns these messages in:

• PowerShell: Error: failed to unmarshal json. invalid character 'h' looking for beginning of value
• CMD: Error: Unknown Command "API.HTTPHeaders.Access-Control-Allow-Origin"

Valid forms of this are:

• PowerShell: ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin '[\"http://127.0.0.1:8080\", \"http://127.0.0.1:5001\", \"https://webui.ipfs.io\"]' ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods '[\"PUT\", \"GET\", \"POST\"]'
• CMD: ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin "["""http://127.0.0.1:8080""", """http://127.0.0.1:5001""", """https://webui.ipfs.io"""]" ipfs config --json API.HTTPHeaders.Access-Control-Allow-Methods "["""PUT""", """GET""", """POST"""]"

It would be nice if the shell element had some way to select what command shell you’re using, and formatted the string so the arguments matched the escape type.

[abdenoursouidi]

You are a hero ♥

[itm-platform]

Hi there, I tried both (Windows 11)

• PowerShell: ipfs config --json API.HTTPHeaders.Access-Control-Allow-Credentials '[\"true\"]'
• CMD: ipfs config --json API.HTTPHeaders.Access-Control-Allow-Credentials "["""true"""]" And I get in both cases

 failure to decode config: json: cannot unmarshal string into Go struct field API.API.HTTPHeaders of type []string

I also tried all forms of adding the config file

  "API": {
    "HTTPHeaders": {
	"Access-Control-Allow-Origin": "['*']"
	}
  }

But I get the same error. Any ideas?