-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
ReadAssetBytesError::Io
exposes failing path
#10450
ReadAssetBytesError::Io
exposes failing path
#10450
Conversation
Welcome, new contributor! Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨ |
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
@orph3usLyre CI failures look real; can you test this out locally and then push the changes? Once that's done I'm happy to merge this in :) |
# Objective Addresses #[10438](bevyengine#10438) The objective was to include the failing path in the error for the user to see. ## Solution Add a `path` field to the `ReadAssetBytesError::Io` variant to expose the failing path in the error message. ## Migration Guide - The `ReadAssetBytesError::Io` variant now contains two named fields instead of converting from `std::io::Error`. 1. `path`: The requested (failing) path (`PathBuf`) 2. `source`: The source `std::io::Error` --------- Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Objective
Addresses #10438
The objective was to include the failing path in the error for the user to see.
Solution
Add a
path
field to theReadAssetBytesError::Io
variant to expose the failing path in the error message.Migration Guide
ReadAssetBytesError::Io
variant now contains two named fields instead of converting fromstd::io::Error
.path
: The requested (failing) path (PathBuf
)source
: The sourcestd::io::Error