Skip to content

Releases: multiversx/mx-ide-vscode

v0.21.1

01 Feb 15:30
9071d29
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.21.0...v0.21.1

v0.21.0

11 Dec 12:00
1abf02c
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.20.0...v0.21.0

v0.20.0

27 Sep 08:55
eafec46
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.19.0...v0.20.0

v0.19.0

18 Sep 09:29
c8cde21
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.18.0...v0.19.0

v0.18.0

21 Mar 11:11
b850f6f
Compare
Choose a tag to compare

Discord announcement (before release).

🟢 The extension does not patch settings.json anymore

We've decided to not automatically patch settings.json anymore. It's the responsibility of the VSCode user 💪 to adjust settings.json and include necessary PATHs and variables, if needed - e.g. if the user relies on the Rust installation in ~/multiversx-sdk as opposed to a separate Rust installation.

Please find below an example of adjusting settings.json, if you rely on the ~/multivers-sdk installation of Rust (also note the alteration of PATH).

For Linux:

{
    "terminal.integrated.env.linux": {
        "PATH": "${env:HOME}/multiversx-sdk:${env:HOME}/multiversx-sdk/vendor-rust/bin:${env:HOME}/multiversx-sdk/vmtools:${env:PATH}",
        "RUSTUP_HOME": "${env:HOME}/multiversx-sdk/vendor-rust",
        "CARGO_HOME": "${env:HOME}/multiversx-sdk/vendor-rust"
    },
    "rust-analyzer.server.extraEnv": {
        "RUSTUP_HOME": "${env:HOME}/multiversx-sdk/vendor-rust",
        "CARGO_HOME": "${env:HOME}/multiversx-sdk/vendor-rust"
    }
}

For MacOS:

{
    "terminal.integrated.env.osx": {
        "PATH": "${env:HOME}/multiversx-sdk:${env:HOME}/multiversx-sdk/vendor-rust/bin:${env:HOME}/multiversx-sdk/vmtools:${env:PATH}",
        "RUSTUP_HOME": "${env:HOME}/multiversx-sdk/vendor-rust",
        "CARGO_HOME": "${env:HOME}/multiversx-sdk/vendor-rust"
    },
    "rust-analyzer.server.extraEnv": {
        "RUSTUP_HOME": "${env:HOME}/multiversx-sdk/vendor-rust",
        "CARGO_HOME": "${env:HOME}/multiversx-sdk/vendor-rust"
    }
}

🟢 No more support for running bash snippets from the UI

Rust-based contract interaction snippets will arise soon 🦀 . We've dropped support for invoking bash interaction snippets directly from the VSCode extension (user interface).

Existing bash-based interaction snippets can still be invoked from the CLI, as follows (example for the adder contract):

export PROJECT=$(pwd)
export USERS=~/multiversx-sdk/testwallets/latest/users

source interactions/testnet.snippets.sh && deploy
source interactions/testnet.snippets.sh && add

What's Changed

Full Changelog: v0.17.0...v0.18.0

v0.17.0

17 Feb 10:57
7cb27ab
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.16.1...v0.17.0

v0.16.1

31 Jan 08:10
d5e4752
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.16.0...v0.16.1

v0.16.0

19 Jan 12:41
19441e6
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.15.0...v0.16.0

v0.15.0

18 Jan 16:03
3eaa67f
Compare
Choose a tag to compare

Upgrade from erdpy to mxpy directly from the IDE 🚀

Also see: https://github.com/multiversx/mx-sdk-py-cli/releases/tag/v5.0.1

What's Changed

  • Handle SDK renaming: elrondsdk -> multiversx-sdk, erdpy -> mxpy by @andreibancioiu in #64

Full Changelog: v0.14.1...v0.15.0

v0.14.1

11 Jan 16:04
f83e943
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.14.0...v0.14.1