You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a monorepo or something similar (e.g. a tauri app) and you have your Rust code in a non-workspace-root folder - the vscode extension fails to detect that we have a cargo project that uses insta and does not find pending snaps etc.
Reproduction steps
mkdir -p monorepo/rust-crate
cd monorepo/rust-crate
cargo init
cargo add --dev insta
cd ..
code .
Insta Version
1.38.0
rustc Version
1.76.0
What did you expect?
I think the extension should detect folders with Cargo.toml (also consider workspaces ig) and use those as the rootUri instead of the workspace root.
Maybe communicate with rust-analyzer extension (if it's possible/simple, don't know much about vscode extensions) which definitely does detect cargo projects in the workspace and probably does so most robustly.
The text was updated successfully, but these errors were encountered:
What happened?
If you have a monorepo or something similar (e.g. a tauri app) and you have your Rust code in a non-workspace-root folder - the vscode extension fails to detect that we have a cargo project that uses insta and does not find pending snaps etc.
Reproduction steps
Insta Version
1.38.0
rustc Version
1.76.0
What did you expect?
I think the extension should detect folders with Cargo.toml (also consider workspaces ig) and use those as the rootUri instead of the workspace root.
Maybe communicate with rust-analyzer extension (if it's possible/simple, don't know much about vscode extensions) which definitely does detect cargo projects in the workspace and probably does so most robustly.
The text was updated successfully, but these errors were encountered: