Test: Support for WSL

[mrsauravsahu]

related: #6 #7

[mrsauravsahu]

Testbed:
Windows 10 v21H1 (OS Build 190.43.1081)
VSCode 1.58.0 with ms-vscode-remote.remote-wsl extension installed

Functionalities working:

• ✔ create custom profiles
• ✔ View featured profiles

Fail

• ❌ Unable to launch custom profile from 'Custom Profiles Explorer'
• ❌ View details of a custom profile
• ❌ Launch Custom Profile from .vscode/profile.json

[DeadlyChambers]

Has this been tested on WSL lately?

[mrsauravsahu]

Tested this recently, unfortunately, custom locations for user data and extensions aren't supported on WSL.

$ code --user-data-dir '/home/sauravsahu/.config/vscode-manager/arrogant-roundworm/data' --extensions-dir '/home/sauravsahu/.config/vscode-manager/arrogant-roundworm/extensions' -n
Ignoring option user-data-dir: not supported for code.
Ignoring option extensions-dir: not supported for code.

$ code -v
1.69.0
92d25e35d9bf1a6b16f7d0758f25d48ace11e5b9
x64

[mrsauravsahu]

Now that I think about it, I think most of the vscode-manager commands should be run on the host as opposed to the remote (WSL) for this. As long as that is supported, we should be able to get this working.