Add an activation command for other extensions

[gtaylor]

Context

Since VS Code provides no actionEvents that trigger when a specific extension activates, extensions can't activate only once Roo is activated and ready. This means that all other extensions have to activate at IDE time and poll for dependent extension(s). This leads to reinvented boilerplate and can also negatively impact VS Code start times.

As some added context, my company is writing a separate extension that manages Roo's configuration. We want to activate this extension once/only if Roo is already activated.

Implementation

This commit introduces a new roo-cline.activationCompleted command and fires it at the very end of extension activation. Other extensions that use Roo's exported APIs can now activate when they see this event.

Note that I have not added the command to package.json since I don't want it to show up in the command palette.

How to Test

• Stick a temporary vscode.window.showWarningMessage into the command definition and start VS Code + Roo in dev mode.
• You should see your warning message
• If you're feeling especially motivated you can go a step further:
  • Create another extension
  • Set it up to activate on roo-cline.activationCompleted events
  • Have it fire off a log/print/message when the dependent extension activates

---

Important

Adds roo-cline.activationCompleted command to signal Roo extension activation completion for dependent extensions.

• Behavior:
  • Adds roo-cline.activationCompleted command in registerCommands.ts to signal Roo extension activation completion.
  • Executes roo-cline.activationCompleted in activate() in extension.ts to notify dependent extensions.
• Misc:
  • Command not added to package.json to prevent it from appearing in the command palette.

^{This description was created by for 08ce786. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 08ce786

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR