Add depending bevy features for higher level one #7855
Merged
+6
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
Typically, when using a bevy feature such as
bevy_pbr
in combination withthe
no-default-features
system, users will need to spawn a camera,sometimes manipulate meshes. Which requires enabling other bevy features.
The process of finding what features need to be enabled is time consuming
and frustrating, as the error messages do not give a hint as of what needs to
be done.
Solution
This commit adds those features as dependencies of "higher level"
features, so that the end user is not burdened with hunting which
feature need which other feature. And everyone was happy
eversoafter.
Note that since the higher level crates already depend internally
on lower level crates, the only compilation time increase would
be when generating the
bevy
doc (because seemingly,rustdoc
is very slow at resolving re-exports)Changelog
bevy_pbr
now automatically adds lower level features (such asbevy_core_pipeline
andbevy_render
)