Integration question

[MatthiasHofstaetter]

Hello!
I am currently working on integrating the vscode extension of this repo into my own project.
I made a subfolder in my project which has the same classes as the subfolder of packages/open-collaboration-vscode/src to provide the extension logic.

Then i integrated the setup of the commands in my own extension activate function, as you did in this repo

    const container = createContainer(context);
    const commands = container.get(Commands);
    commands.initialize();

The Problem i am facing is following:
With my implementation it worked once to start my project and get the connection between the extension and the local code of my repository. So i started my extension, and the copied code of your repo was accessed locally in my repo, for example for "createRoom" in the roomservice.
I started my extension, clicked the opencollaboration icon, clicked "Create new Collaboration Session" and the createroom function of my project was called.

But now when i run my code and try to register the commands in the extension activate method i run into the error that all the oct.* commands have already been registered. So no registration -> my local code is not executed, but the code from the extension within.

I tried and debugged your implementation of this repository and saw that when i enter your activate() function of the extension it works because the oct. commands are not yet registered within vscode, as it should be.
But with my project it now seems as the oct.* commands are already there after installing the extension in vscode? (I tried to uninstall the extension and re-run my code -> no commands were registered).

So my question is, is there a switch i did not see in your repo to avoid to register the oct.* commands when installing the open-api-collaborations extension so no commands are registered upon startup?

Best regards.

[msujew]

Hey @MatthiasHofstaetter,

are you running your fork of the VS Code extension in parallel with our VS Code extension? As that would very much explain why it would throw the error. First, our extension starts, registers the commands, which then already exist when your extension start -> VS Code throws errors about duplicate command registrations.

Aside from that, is there a specific reason you're copying the VS Code extension? Not that we have anything against it (the code is MIT on purpose), but as times goes on, it will be rather difficult to keep up with the underlying server protocol changes. Or do you have your own fork of the server code as well?

[MatthiasHofstaetter]

hey!
Thank you for the quick reply!

No i am not running a fork in parallel.
When i start the extension of your implementation (so this repo) in my opinion it should be the same case. The extension is installed and the activate function is called -> the commands are not registered.
So i run your extension -> activate method gets called and no commands are registered.
When i start my extension and try to register the commands they are already there.

For context i am currently in analysing for a diploma thesis to enhance the following repo with a collaboration feature:
https://github.com/eclipse-glsp/glsp-vscode-integration

Collaboration with liveshare is already implemented and i want to use your protocol to do the collaboration.
For that purpose i need to access the vscode extension code to use the protocol.
As i found the collaborationInstance stores the information i need to access for that (for example if user is host or not etc.).
And i did not find a hint how to access the extension otherwise, like LiveShare has a getApi() call to get use of the extension for example.

Did i miss something or is there a other way the use of the extension is supposed to be?

[msujew]

like LiveShare has a getApi() call to get use of the extension for example.

We plan to do something similar soon, but we didn't have an opportunity to work on that yet.

No i am not running a fork in parallel.

I made a subfolder in my project which has the same classes as the subfolder of packages/open-collaboration-vscode/src to provide the extension logic.

I'm confused. That sounds like a fork of our project (even if it's not a git fork), but maybe it's just semantics. It's a copy, right? Anyway, I'm not sure why the commands aren't getting registered. Can you provide a reproducible example?