-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - Remove Bytes, FromBytes, Labels, EntityLabels. Document rest of bevy_core and enable warning on missing docs. #3521
Conversation
I'll defer to @maniwani (Joy) here; they've thought most deeply about this. |
Does this PR require a migration guide? Not sure how many users were dependent on those public types, including the ones made private. |
Yep, we'll toss it in the tag. It's not critical, but it is nice to have some indication that we made breaking changes. |
Looks great; only a couple things to expand on. |
Migration Guide for this PR:
|
You should also note that some of the state for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll be sad to see Labels
go away, but it's the right thing to do 👍
bors r+ |
…core and enable warning on missing docs. (#3521) This PR is part of the issue #3492. # Objective - Clean up dead code in `bevy_core`. - Add and update the `bevy_core` documentation to achieve a 100% documentation coverage. - Add the #![warn(missing_docs)] lint to keep the documentation coverage for the future. # Solution - Remove unused `Bytes`, `FromBytes`, `Labels`, and `EntityLabels` types and associated systems. - Made several types private that really only have use as internal types, mostly pertaining to fixed timestep execution. - Add and update the bevy_core documentation. - Add the #![warn(missing_docs)] lint. # Open Questions Should more of the internal states of `FixedTimestep` be public? Seems mostly to be an implementation detail unless someone really needs that fixed timestep state.
Only |
Pull request successfully merged into main. Build succeeded! And happy new year! 🎉
|
This PR is part of the issue #3492.
Objective
bevy_core
.bevy_core
documentation to achieve a 100% documentation coverage.Solution
Bytes
,FromBytes
,Labels
, andEntityLabels
types and associated systems.Open Questions
Should more of the internal states of
FixedTimestep
be public? Seems mostly to be an implementation detail unless someone really needs that fixed timestep state.