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.
Hello! I'd like to use your crate in 0.15. There are a few snags upgrading detailed below. Not sure how you'd like me to handle these. In general though, the upgrade works!
all-features
to true for dev-dependencies. Workaround for Compilation Failure: Regression in enablingbevy_gltf
feature bevyengine/bevy#16671piano.rs
) to use updated Components (Existing bundles were deprecated.TextSection
appears to have been removed)bevy_mod_picking
is not ready for 0.15: Bevy 0.15 aevyrie/bevy_mod_picking#375. This dependency is used by thepiano
example. I'll see to removing itinput.rs
always panics on connect on my computer, including on the main branch. I'll look to fix.I'm not sure how you would like to proceed on the
piano.rs
example. I think this example is possible without this dependency.Additionally, would it be alright to lock dependency versioning for this crate (remove
Cargo.lock
from.gitignore
)? I would like to ensure consistent behavior for this crate since bevy is a tumultuous ecosystem.