targrub
targrub
My initial solution runs locally in ~27s in debug, ~2.7s in release (for which no instructions were given [spoiler: cargo test -r]). The test runner on the server must also...
Completely agree with all you said, Peter. And now I learned about the existence of `lines()`.
Tests in code should make explicit what functionality is expected. (Code is law?)
I mean someone ought to write tests for the `Commands` methods to demonstrate how they ought to work. The documentation can be incorrect/misleading, but having code which demonstrates the intention...
For example, if the `Commands` are actually applied at a certain `Stage` of the overall ECS system's operation, a set of tests could make that clear. I have no objection...
You're right; reverting my changes to `bevy_svg`'s `Cargo.toml` and running it as you suggest got the example working again. However, if I do this: ``` [dev-dependencies] bevy = { version...
Doesn't this need documentation changes? Migration instructions?
> Oh, I missed #6114, which seems to make almost the same changes with mainly different intention / language around them. It also adds a test example and changes the...
> I'm going to merge targrub's PR first to spare them the git pain :) I also think it's less complex / controversial than this change. Gee, thanks!
Taking the first crate on the list currently missing documentation, `bevy_core_pipeline`, my best judgement (based mostly on those who originally checked in the code in its present location) is that...