forestia/bevy
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

impl Debug for ExtendedMaterial (#14140)

Browse Source 
# Objective

Both `Material` and `MaterialExtension` (base and extension) can derive
Debug, so there's no reason to not allow `ExtendedMaterial` to derive it

## Solution

- Describe the solution used to achieve the objective above.
Add `Debug` to the list of derived traits

## Testing

- Did you test these changes? If so, how?
I compiled my test project on latest commit, making sure it actually
compiles
- How can other people (reviewers) test your changes? Is there anything
specific they need to know?
Create an ExtendedMaterial instance, try to `println!("{:?}",
material);`

Co-authored-by: NWPlayer123 <NWPlayer123@users.noreply.github.com>
This commit is contained in:
NWPlayer123 2024-07-04 17:59:48 -06:00 committed by GitHub
parent 5986d5d309
commit c6a89c2187
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
crates/bevy_pbr/src/extended_material.rs
View File

@ -121,7 +121,7 @@ pub trait MaterialExtension: Asset + AsBindGroup + Clone + Sized {
/// When used with `StandardMaterial` as the base, all the standard material fields are /// When used with `StandardMaterial` as the base, all the standard material fields are
/// present, so the `pbr_fragment` shader functions can be called from the extension shader (see /// present, so the `pbr_fragment` shader functions can be called from the extension shader (see
/// the `extended_material` example). /// the `extended_material` example).
#[derive(Asset, Clone, Reflect)] #[derive(Asset, Clone, Debug, Reflect)]
#[reflect(type_path = false)] #[reflect(type_path = false)]
pub struct ExtendedMaterial<B: Material, E: MaterialExtension> { pub struct ExtendedMaterial<B: Material, E: MaterialExtension> {
pub base: B, pub base: B,