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
Currently, we export all types that have been registered in bevy_reflect.
While it works, this is sub-optimal: in the end, we are only interested in the types we will be actually able to use, ie. Components and Resources. It leads to a lot of clutter in the TIled interface.
A solution to this would be to only register types that either:
derive ReflectComponent or ReflectBundle trait
derive ReflectResource trait
are used by a type which derive one of these traits (this is actually the hard part)
The text was updated successfully, but these errors were encountered:
* Restrict Tiled exports only to Components and Resources #50
* Support non-unit enums user properties #49
* fix: prevent infinite loop in case an asset fails to load
* feat: improve how we handle default values for user properties
---------
Co-authored-by: Niashi <[email protected]>
Currently, we export all types that have been registered in
bevy_reflect
.While it works, this is sub-optimal: in the end, we are only interested in the types we will be actually able to use, ie. Components and Resources. It leads to a lot of clutter in the TIled interface.
A solution to this would be to only register types that either:
ReflectComponent
orReflectBundle
traitReflectResource
traitThe text was updated successfully, but these errors were encountered: