Done use pub use module::*
re-export style
#17268
Labels
A-Cross-Cutting
Impacts the entire engine
C-Code-Quality
A section of code that is hard to understand or change
C-Docs
An addition or correction to our documentation
D-Trivial
Nice and easy! A great choice to get started with Bevy
S-Ready-For-Implementation
This issue is ready for an implementation PR. Go for it!
X-Contentious
There are nontrivial implications that should be thought through
The "pub use module::*`" style in bevy_ui is pretty terrible for documentation: both because "pile of stuff" and because it breaks module docs.
I've broken from convention here: I would like to change the other modules in this crate in another PR.
Originally posted by @alice-i-cecile in #17267 (comment)
There may be other instances of this pattern that I would like to clean up.
The text was updated successfully, but these errors were encountered: