For less undesired side-effects, the extension does not automatically patch settings.json anymore. It's the responsibility of the VSCode user to adjust settings.json and include necessary PATHs and variables - only as needed (e.g. if the user does rely on the Rust installation in ~/multiversx-sdk as opposed to a separate installation):
Rust-based contract interaction snippets will arise soon.
Writing contract interaction snippets in bash is now discouraged. We've dropped support for invoking such interaction snippets directly from the VSCode extension UI.
Existing bash-based interaction snippets can still be invoked from the CLI, as follows (example for the adder contract):
1
For less undesired side-effects, the extension does not automatically patch
settings.json
anymore. It's the responsibility of the VSCode user to adjustsettings.json
and include necessary PATHs and variables - only as needed (e.g. if the user does rely on the Rust installation in~/multiversx-sdk
as opposed to a separate installation):For Linux:
For MacOS:
2
Rust-based contract interaction snippets will arise soon.
Writing contract interaction snippets in bash is now discouraged. We've dropped support for invoking such interaction snippets directly from the VSCode extension UI.
Existing bash-based interaction snippets can still be invoked from the CLI, as follows (example for the
adder
contract):3
In the past, we've patched both
launchItems
andtasks
collections oflaunch.json
andtasks.json
. Now we don't anymore.4
Do not patch anymore
.gitignore
. This must be the responsibility of the user (with aid from the contract template system).