jimasp
commented
5 months ago The current version of the extension works ok, but from a source/change perspective, the code is very unstable and still undergoing large rewrites which is more likely to result in bugs. A large part of this is because the vscode test API is still new and evolving, which means my code has to evolve along with it, but also due to my misunderstanding about certain aspects of vscode api usage and/or behave quirks that improve over time.
Settings.json settings may also change radically between releases which is ok for pre-release but less desirable once you get to an official release. Basically, I don't want to give people the impression that the extension is stable when it is not.
While this would normally be solved by having a separate pre-release version and a release version, I simply don't have the time/inclination to maintain two versions, i.e. it would eat in to the time I have to work on the extension.
In theory, the current plan for a proper release is probably when I hit version 0.9.0. (The next release due is 0.7.0, which is the largest remaining release). I don't have a timescale to hit an official release as I don't have much free time atm.
If you need an official release urgently, remember that this code is MIT, so you could fork the code, then replace every instance of "Behave VSC" and "behave-vsc" in the code with a different name, and then publish your own renamed version of the extension and use that until there is an official release.
I have a simple request: I'd like to have an official release of this great plugin. As it works pretty well for, I would not see a blocker. This would make things easier when it comes to sharing the workspaces with others.