Closed elenakrittik closed 9 months ago
I personally totally share your vision and if breaking changes are for the better, then i'll make them. But at the same time i recognize that there's a plenty of developers with busy schedules and that they would rather prefer to receive bug fixes without the accompanying breaking changes. Though, in case of Bevy's ecosystem, i imagine most people will be fine with breaking changes, or pin bevy-related dependencies to specific versions and upgrade only when they're ready. I'll change this PR a bit later.
Done. Due to removal of backwards compatibility had to add lots of #[derive(Default)]
s.
Done, sorry for this simple change taking so long.
Changes the default behavior to use bundle's struct's
Default
impl
instead of each individual field's.Solves #119.
cargo fmt
.cargo test
.cargo clippy
and fixed any issues arising from my changes.