marcantoineg / code-profiles

Extensions manager for VS Code ⚙️

code-profiles 💻

Simply, what is it?

Profiles for VS Code Extensions.

I use this to load only the extensions I need in VS Code depending on projects.

How does it work?

You need 2 things:

• a code-profiles.yml where your executable is. This is where you define your profiles.
• a .code-profile with a valid profile name. This will start VSCode using --extensions-dir with the right extensions.

You have multiple commands:

• open: which opens VSCode with a specified profile.
  From the .code-profile file in the current working directory or args (code-profiles open [profile_name])
• install: which installs required extensions for a specified profile.
  From the .code-profile file in the CWD or args (code-profiles install [profile_name])

Usage

Basic commands:

Usage:
  code-profiles [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  install     install required VSCode extensions for a given profile
  open        open VSCode using a custom profile for extensions

Flags:
  -h, --help   help for code-profiles

install

install required VSCode extensions for a given profile

Usage:
  code-profiles install [profile_name] [flags]

Flags:
  -c, --config-path string   Path to code-profiles config (default "./code-profiles.yml")
  -h, --help                 help for install
  -v, --verbose              prints additional logs

open

open VSCode using a custom profile for extensions

Usage:
  code-profiles open [profile_name] [flags]

Flags:
  -c, --config-path string   Path to code-profiles config (default "./code-profiles.yml")
  -h, --help                 help for open
  -i, --install              should install extensions before opening VSCode
  -v, --verbose              prints additional logs

code-profiles's Issues

add Release workflow

🔗 references

for example

configurable `code-profiles.yml` location

add someway to configure where to load the profiles from

add an `install` command

you can install through the open -i command but a standalone command would be nice

update `README.md`

📖 Description

• add Usage section to readme.
• rework Decription section.
• add CI badge

look at installed package & skip install if not required

Description 📖

Either compare missing extensions with what's installed and install only what's required or skip them altogether if everything is installed already.

document stuff

Description 📖

Write doc for:

• utils.go
• config.go
• open.go?

add tests to all modules

Description 📖

Write tests for:

• utils.go
• config.go
• #9 (moved to its own issue)
• #10 (moved to its own issue)

test `code.go`

not 100% sure how to test this.

test `open.go`

It'll take some learning to test this section.

Refactor YAML property `profile-path`

Description 📖

Since it's not the "profile's path" but more precisely the "extensions installation path", it should be renamed.

Document each commands in the README

Description 📖

Have a section in the README that exposes all commands and all flags for each command.

• code-profiles
• open
• install

create gif/screenshots for `readme`

📷 requirements

• a blank vscode
• a vscode with a profile loaded

Beautify `-v` mode

Description 📖

• Add what extensions & version were installed (--list-extensions / --show-versions)

References 🔗

https://code.visualstudio.com/docs/editor/command-line#_working-with-extensions

add a `--verbose`, `-v` flag

use verbose mode to enable printing of code commands output.

test `install.go`

Description 📖

Make sure it installs at the right place whether it's a:

• relative path
• absolute path
• path that starts with ~

Installation never actually happens

Description 📖

After deleting what was already installed from another version, I can't seem to install anything anymore.

STR

• rm -rf a profile's path
• code-profiles open -i or code-profiles install the deleted profile
• see that it seems to install the profile & launch vscode but the extensions are not installed in the profile's path.

resolve `~` to actual user's home

you know

force install extensions

Add a flag (-f, --force) on the install command to either delete the profile folder, then reinstall all extensions, or force install/update all extensions if possible.

_{*Deleteing the profile folder should be avoided in case the user puts something else in there for some reason.}