There should be a to not rely on CARGO_MANIFEST_DIR to exist at runtime.

[Fuuzetsu]

For various reasons, we do our builds it a temporary location. This means that anything that uses assert_snapshot gets the temporary location embedded into the binary via the env!("CARGO_MANIFEST_DIR"). Once we go onto trying to run the test binary produced during the build, it fails.

Having said that, we run the test binaries with sources (and so also with snapshots) available: therefore insta should be able to find the files but it insists on using manifest_dir for all its queries which is a location that doesn't exist.

It would be extremely useful to be able to tell insta at runtime of where it should try to find out the workspace metadata. For us this would just be pwd.

[Fuuzetsu]

A simple way would be to add something like:

let manifest_dir = std::env::var("INSTA_MANIFEST_DIR").unwrap_or(manifest_dir);

This would allow whatever system to set the variable at runtime and everyone is happy.