Move dynamic plugin loading to its own crate #415
Labels
A-Build-System
Related to build systems or continuous integration
C-Code-Quality
A section of code that is hard to understand or change
D-Trivial
Nice and easy! A great choice to get started with Bevy
Currently we are utilizing features to selectively enable/disable dynamic plugin loading code throughout the bevy codebase. @Dispersia had the good idea to move this to a separate crate, which I think should be possible. This would simplify the cargo features and move all of the dynamic plugin loading code to one spot.
The text was updated successfully, but these errors were encountered: