4340f7b7c6
# Objective Explicitly and exactly know what of the environment variables (if any) are being used/not-used/found-not-found by the `bevy_asset::io::file::get_base_path()`. - Describe the objective or issue this PR addresses: In a sufficiently complex project, with enough crates and such it _can_ be hard to know what the Asset Server is using as, what in the bevy parlance is its 'base path', this change seems to be the lowest effort to discovering that. ## Solution - Added `debug!` logging to the `FileAssetReader::new()` call. ## Testing See output by making a project and trying something like `RUST_LOG=bevy_asset::io::file=debug cargo run` - Ran Bevy's tests. - How can other people (reviewers) test your changes?: Intentionally mess with your `env` variables (BEVY_ASSET_ROOT and CARGO_MANIFEST_DIR, scatter assets about and attempt to (without this change) locate where it's going wrong. - Is there anything specific they need to know?: I encountered this issue in a rather large workspace with many many crates with multiple nested asset directories. - If relevant, what platforms did you test these changes on, and are there any important ones you can't test? Linux. --- |
||
|---|---|---|
| .. | ||
| io | ||
| processor | ||
| server | ||
| assets.rs | ||
| direct_access_ext.rs | ||
| event.rs | ||
| folder.rs | ||
| handle.rs | ||
| id.rs | ||
| lib.rs | ||
| loader_builders.rs | ||
| loader.rs | ||
| meta.rs | ||
| path.rs | ||
| reflect.rs | ||
| saver.rs | ||
| transformer.rs | ||