AnimatableProperty trait's get_mut signature should access to resource

[guzuomuse]

What problem does this solve or what need does it fill?

to problem will be solved: can not update assets in get_mut
A description of why this particular feature should be added.
let mesh_material_3d = entity .get_mut::<MeshMaterial3d<StandardMaterial>>() .ok_or(AnimationEvaluationError::ComponentNotPresent(TypeId::of::< MeshMaterial3d<StandardMaterial>, >( )))? .into_inner();
now we have a MeshMaterial3d Component With a StandardMaterial resource, we have no way to access the referrenceof the StandardMaterial without the help of Asset,

What solution would you like?

offer another paramerter for get_mut ,or add some method to entity ,to have ability to access resource;

[viridia]

I have run into this problem as well. More broadly, I would really like a unified approach where I can animate both component properties (which is what the current animation framework allows), and shader uniforms (not just StandardMaterial, but custom shaders as well), which is currently not supported. All within a single animation timeline.

Consider the current disparity between Sprites and Bevy primitives: with a sprite, you can animate the color because the color is a component property. But you can't animate the color of a primitive mesh in the same way, because the base color lives in the shader asset.

I'm not expecting a magical macro which let's me tweak an arbitrary property of an asset: I fully expect that I will have to write my own implementation of AnimatedProperty. But that's OK.

I realize that there's a potential for ambiguity here: a shader asset might be shared between multiple entities, so animating a uniform might have unexpected consequences if I am not careful. However, I think the burden is on me to ensure that my shader instances are set up in a way that mutation of uniforms does what I expect.