You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With bevyengine/bevy#9140 it will be possible to opt out of type path derivation when deriving reflect and provide a custom implementation (f.i. using std::any::type_name). This enables us to register the configuration component types again, which were temporarily removed when upgrading to bevy 0.11.0
The text was updated successfully, but these errors were encountered:
With bevyengine/bevy#9140 it will be possible to opt out of type path derivation when deriving reflect and provide a custom implementation (f.i. using
std::any::type_name
). This enables us to register the configuration component types again, which were temporarily removed when upgrading to bevy 0.11.0The text was updated successfully, but these errors were encountered: