Open Glandos opened 3 years ago
Came here to post this very issue, glad to see you're already on it @Glandos . Anyone from Mozilla/Firefox able to speak to this? It's pretty trivial to set up.
@hbenl is there any chance that firefox team set up automatic publishing on open-vsx marketplace ?
The version you published two years ago is outdated and of no use on current versions of VSCodium (it simply doesn't work). I'm a teacher and telling my students that they have to manually download this extension on MS marketplace instead of just installing it from extension panel is frustrating since the debugging in google chrome just works out of the box without any additional extension.
As @Glandos said, there is a workaround to publish the extension by ourselves without FF team's participation, but this solution is really not something that matches the "pro" level that this FF extension should have ("extensions published via publish-extensions display a warning that the publisher (this repository) is not the official author" cf. https://github.com/open-vsx/publish-extensions)
Are there any plans to update / keep up to date this extension ?
Dropping by to thank @t-fritsch for mentioning this. I have been debugging my VS Codium installation all day, digging through this repo, wondering why didn't I even receive debug messages for PathConversion
and my breakpoints were all unverified, and finally found out it's because the Open-VSX marketplace has an outdated version of this plugin that no longer works. Installing the VSIX manually did the trick.
Could we get the Open-VSX version of the plugin updated? Or at least a disclaimer in the docs mentioning that it no longer works.
Tagging @hbenl, since it seems he was the one to publish it on Open-VSX the first time.
This extension is currently available on VisualStudio Marketplace, which can only be legally used by the Microsoft build of VSCode. Since this is a non-free build, I am using VSCodium, which is using OpenVSX as its marketplace.
This extension was published on OpenVSX, but it is unofficial, and it is not up-to-date. The best option would be to follow the documentation to create a namespace and upload the extension there. Of course, this requires some work. There is an easiest path, but it should be used by extension users as a wish list.