Skip to content

lsp-rust: fix definition of lsp-rust-analyzer-cargo-extra-env (#4768) #4787

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

miyabinomuratic
Copy link

In rust-analyzer, cargo.extraEnv has been a map since its introduction (rust-lang/rust-analyzer@c407cc5). The definition in lsp-mode hasn't matched since then, but the mismatch has been silently ignored. From rust-lang/rust-analyzer@46ce474, rust-analyzer started showing a warning message on configuration error which we are seeing.

With this change, the definition for cargo.extraEnv should match and the warning message is not displayed.

…lsp#4768)

In rust-analyzer, cargo.extraEnv has been a map since its
introduction (rust-lang/rust-analyzer@c407cc5). The definition in lsp-mode
hasn't matched since then, but the mismatch has been silently ignored. From
rust-lang/rust-analyzer@46ce474, rust-analyzer started showing a warning message
on configuration error which we are seeing.

With this change, the definition for cargo.extraEnv should match and the warning
message is not displayed.
@github-actions github-actions bot added rust client One or more of lsp-mode language clients labels May 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client One or more of lsp-mode language clients rust
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants