BoundaryML
Working with vscode extension and old versions
Maybe theres a setting i'm missing, so appologies if im missing something.
I'm a heavy user of the baml vscode extension, and a frustration i've had is that the extension automatically updates, and starts complaining if i'm not on the very latest version of baml in the generator configuration. Besides being tedious to constantly keep it up to date every time a new version is release, a bigger problem is that if i'm blocked from updating to the latest version (as I am right now due to some bugs in the current version), then the extension becomes more difficult to use.
Am i missing some configuration that would allow me to use the extension without constantly being on the newest version? In an ideal world i would imagine having a setting where i can point to the installed version of baml (in .venv for example) that the extension uses, so it always just uses the latest engine.
![linear[bot] avatar](https://avatars.githubusercontent.com/in/20150?v=4 "Published by a pub.dev verified publisher"){kind=small}
@antoniosarosi is working on a fix! This is definitely our biggest painpoint.
For now, you can go to VSCode settings for the extension, and uncheck "autoupdate"
for some more technical details, the extension will in the future download the right baml-cli for the generator version you have defined, and will just use that, vs the bundled version (which is the latest one). We hope to get this out in the next 1-2 weeks.
What happens if the extension i have installed is older then the referenced version? Do i get the same errors? If so i have to disable it at the right time, but theres no way for me for examlpe right now to make it compatible with 0.72.0 right?
Sounds good that it will auto download right version!
you can install a specific version that matches the one you want to stay on:
If versions dont match it will complain (if it's older or newer). So downloading the right version and disabling autoupdate is the current workaround.
Closing: we also no longer ask users to update nearly as aggressively as we used to
