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

Check workspace with all targets in vscode, emacs configs #205

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

tomasol
Copy link
Contributor

@tomasol tomasol commented Jan 11, 2024

Add --workspace and --all-targets switches to both vscode and emacs configs, that are generated in cargo component new. This is in line with what rust-analyzer uses when
rust-analyzer.check.overrideCommand is empty.
Fixes #203 .

@tomasol
Copy link
Contributor Author

tomasol commented Jan 11, 2024

Looks like main is broken. I'm attempting to fix it in #206

Copy link
Member

@peterhuene peterhuene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for the fix!

When #208 merges, we can rebase this PR on it and get it merged.

Add `--workspace` and `--all-targets` switches to both vscode
and emacs configs, that are generated in `cargo component new`.
This is in line with what rust-analyzer uses when
`rust-analyzer.check.overrideCommand` is empty.
@peterhuene peterhuene force-pushed the 203-fix-vscode-config branch from 58a41f9 to 423a5f7 Compare January 12, 2024 05:55
@peterhuene peterhuene merged commit 356fcac into bytecodealliance:main Jan 12, 2024
6 checks passed
@peterhuene
Copy link
Member

@tomasol thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Generate better cargo check command for vscode
2 participants