Skip to content
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

rust-analyzer.cargo.unsetTest is gone, what should I use as a substitute? #17957

Closed
vittorius opened this issue Aug 25, 2024 · 2 comments · Fixed by #18085
Closed

rust-analyzer.cargo.unsetTest is gone, what should I use as a substitute? #17957

vittorius opened this issue Aug 25, 2024 · 2 comments · Fixed by #18085
Labels
C-support Category: support questions

Comments

@vittorius
Copy link

Some time ago, there was an option to disable the "test feature by default". Now it seems to be gone.
Is there any alternative way to disable the test feature? My primary goal is to disable it for my main crate in order to get rid of the errors highlighted throughout the codebase while my mocks (covered by #[cfg(test)]) are still incomplete.

@vittorius vittorius added the C-support Category: support questions label Aug 25, 2024
@iceHtwoO
Copy link

My fix for now is to downgrade to v0.3.1924, but I would be happy to hear if there is an alternative option. Config was removed with this PR: #16726

@srgsanky
Copy link

I used the following command to downgrade to a version of rust-analyzer that works correctly with unsetTest. 1.79.0 and above starts ignoring unsetTest.

rustup default 1.78.0 && rustup component add rust-analyzer

@bors bors closed this as completed in ceee056 Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-support Category: support questions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants