Open anton-trunov opened 9 months ago
There is no simple way right now. But it is interesting feature for Tact version that has some breaking changes. But at this case we must to have a version number in Tact smart contract code to inform which compiler version need to use. For quick resolution I can suggest to use DEV way: Namely, follow by this documentation https://github.com/tact-lang/tact-vscode/blob/main/README-DEVELOP.md and set version in package.js mannualy. After, run the local version of this extension.
I don't really think this issue has been resolved. There is a workaround, indeed, but from the UX point of view it's certainly not solved. Let me re-open it, to keep track of some features our users (the Tact dev team in this case) might need.
Could you please form how we will solve this issue? Just add an option to the settings that will help to use Tact compiler by the external path, or?
By my opinion, this case will be useful only for DEV and then better to change the compiler version in npm file.
Just I am confused how it will be usefull for the end user, because .tact code doesn't contain the compiler version in own source code.
IMHO, maybe start from the compiler-version
in .tact
files and then add the option which compiler to use for the compilation (or even the needed compiler will be download from the npm repository automatically)
For instance I have a local dev version of the Tact compiler at
$HOME/path-to-tact-repository
and I'd like to use it with the VS Code plugin, what do I do? Is there a setting or some alternative way?