-
Notifications
You must be signed in to change notification settings - Fork 2
add example of a unit test to rainbow-clear-color #99
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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Trouv
reviewed
Dec 27, 2025
Trouv
reviewed
Dec 27, 2025
Trouv
reviewed
Dec 28, 2025
Trouv
reviewed
Dec 29, 2025
d76031d to
bc4e5c3
Compare
Trouv
approved these changes
Dec 29, 2025
Trouv
added a commit
that referenced
this pull request
Jan 15, 2026
🤖 I have created a release *beep* *boop* --- ## [0.2.0](v0.1.0...v0.2.0) (2026-01-15) ### ⚠ BREAKING CHANGES * split ComponentsSetWith into 4 with different generics ([#111](#111)) * upgrade to bevy 0.18 ([#110](#110)) * split ComponentsSet into two with and without filter ([#109](#109)) * split EntityComponentsSetWith into two with and without query data ([#108](#108)) * return simpler CommandSpawn effect from command_spawn constructor ([#107](#107)) ### Features * return simpler CommandSpawn effect from command_spawn constructor ([#107](#107)) ([4b58dea](4b58dea)) * split ComponentsSet into two with and without filter ([#109](#109)) ([b15c1a0](b15c1a0)) * split ComponentsSetWith into 4 with different generics ([#111](#111)) ([4efe59b](4efe59b)) * split EntityComponentsSetWith into two with and without query data ([#108](#108)) ([b362f45](b362f45)) * upgrade to bevy 0.18 ([#110](#110)) ([f12948b](f12948b)) ### Documentation Changes * add 0.2 to compatibility chart in README.md ([#114](#114)) ([8a95fac](8a95fac)) * enable minimal features in mdbook-keeper ([#113](#113)) ([ceb0982](ceb0982)) ### Example Changes * add unit test to rainbow-clear-color example ([#99](#99)) ([f837c0f](f837c0f)) ### CI Changes * exclude component in release-please tag ([#105](#105)) ([2d3e16c](2d3e16c)), closes [#94](#94) * rename book changelog section to docs ([#106](#106)) ([413b4bc](413b4bc)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think one of the biggest values of having a system like this is the ease of unit testing the pure system so a test case should be included. I had to go through a bit of time and effort working out how to do it without too much overhead. There may be easier ways to do this but this is what I came up with.