microsoft
Whitelist new extension for usage of LiveShare features ⁉️
We have developed a LiveShare extension and now want to package it and release it in the marketplace. From our understanding we need have included the extension's publisher + ID in a whitelist which is maintained by you to be able to use LiveShare features.
We're running into the issue that shareService is always returning null when we use our own publisher + ID settings. In development we worked around that by using name and publisher of an existing extension in our package.json.
How to be added to this whitelist? We tried to ask this in https://github.com/MicrosoftDocs/live-share/issues/2896#issuecomment-1138758831 but didn't receive any answers.
What is the suggested procedure to get our extension whitelisted? Thanks a lot!
Hi @fubaduba @daytonellwanger Can you help us out here? We haven't gotten any feedback on how to whitelist a custom LiveShare extension. What is the intended process here? Should we open-source our extension first?
Hey @derekbekoe. Looks like you're one of the maintainers of this repo. It would be great if you could help us out here.
Is our question not at the right place or is it not possible (anymore) to write extensions using the LiveShare API?
Apologies for the delay here and thanks for taking the time to file this issue to submit this request. Unfortunately, we’re not able to prioritize this due to some of the considerations outlined in https://github.com/MicrosoftDocs/live-share/issues/2896#issuecomment-1138758831. If this changes in the future, we'll revisit this. We understand that this may be disappointing. We appreciate your input and comments on this issue till now.
