Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I use a custom Tact version with tact-vscode? #23

Open
anton-trunov opened this issue Feb 15, 2024 · 4 comments
Open

How do I use a custom Tact version with tact-vscode? #23

anton-trunov opened this issue Feb 15, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@anton-trunov
Copy link
Member

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?

@logvik
Copy link
Member

logvik commented Feb 15, 2024

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.

@logvik logvik closed this as completed Feb 25, 2024
@anton-trunov
Copy link
Member Author

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.

@anton-trunov anton-trunov reopened this Feb 25, 2024
@logvik logvik added the enhancement New feature or request label Feb 25, 2024
@logvik
Copy link
Member

logvik commented Feb 25, 2024

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)

@logvik
Copy link
Member

logvik commented Feb 26, 2024

2024-02-26 11_46_01-package json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants