malusev998 / rust-analyzer-downloader

RAD - Rust Analyzer Downloader

Rust Analyzer Downloader

Motivation

1. I always wanted to have rust-analyzer in my $HOME/bin folder, from where I could share it with VSCode and NeoVIM (possibly others if I find them in the future). This was done using bash script without any error handling, which failed from time to time, also I wanted to use Rust for some CLI project and have a little bit more practice with the language and ecosystem and this provided perfect opportunity.

2. Also bash script was not portable to Windows, since i do most of my rust development on Windows PC, this was one deal breaker for me to rewrite the script into Rust.

Usage

rust-analyzer-downloader
Downloads and gets versions for Rust Analyzer

USAGE:
    rust-analyzer-downloader <SUBCOMMAND>

OPTIONS:
    -h, --help    Print help information

SUBCOMMANDS:
    check
    download
    get-versions
    help            Print this message or the help of the given subcommand(s)

Building

cargo build --release

Support

If you are having problems, please let us know by raising a new issue.

License

This project is licensed with the Apache License 2.0.

rust-analyzer-downloader's Issues

Remove tokio as dependency from the library

Test Coverage

Check command with nightly not working

rad check -n

Output:
ERROR main rad: Some error has occurred the 'year' component could not be parsed

Rusttls instead of native-tls

Currently its hard locked to rustls -> better to introduce build feature where rust tls will be allowed

Error on check command when rust-analyzer is not found

Running rad check command when rust-analyzer binary is not found on the system PATH results in an error

ERROR main rad: Some error has occurred program not found

Output directory for Downloader from OS environement variable

Currently output path for rust-analyzer binary is hard coded in the rad binary based on the operating system
$HOME/bin/rust-analyzer

Output path can be changed using CLI flag -o/--output in check and download commands.
This is quite annoying if you need to do it every time when you're updating rust-analyzer.

To mitigate this issue, and not to introduce config file, system environment variable is the best choice to preserve output path.

STDOUT output instead of tokio tracing

Currently for the output tokio::tracing is used, this is ok for printing application logs and errors but not ok for general purpose output.