v0.21.1

What's Changed

• Fix the way mxpy is resolved by @andreibancioiu in #87

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

v0.21.0

What's Changed

• Use newest mxpy (v9) by @andreibancioiu in #85

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

v0.20.0

What's Changed

• Adjust setup, use webpack etc by @andreibancioiu in #75
• Better error management, better display of logs / messages by @andreibancioiu in #76
• Bump version, use newer mxpy, bit of cleanup by @andreibancioiu in #83
• Fix release workflow by @andreibancioiu in #84

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

v0.19.0

What's Changed

• Fix compatibility with mxpy v8 by @andreibancioiu in #81

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

v0.18.0

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

• Remove environment pollution by @andreibancioiu in #73
• Remove custom support for bash snippets by @andreibancioiu in #71
• A bit of workspace cleanup / simplifications by @andreibancioiu in #72

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

v0.17.0

What's Changed

• Do not handle clang / cpp projects anymore by @andreibancioiu in #69

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

v0.16.1

What's Changed

• Fix path for lldb pretty printer script by @andreibancioiu in #68

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

v0.16.0

What's Changed

• Do not natively handle "erdjs-snippets" anymore by @andreibancioiu in #65

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

v0.15.0

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

What's Changed

• Use a monochrome logo for the activity icon by @claudiu725 in #62
• Update telegram link by @claudiu725 in #63

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