-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Refactor the color decode test by using a nested class #819
Refactor the color decode test by using a nested class #819
Conversation
This prevents the variables and their value assignments from having to be repeated four times.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, your first Pull Request in the LITIENGINE repository! You have earned the rank of "contributor" - let us know your nickname in the Forum and on Discord so we can reward you with the new role :).
litiengine/src/test/java/de/gurkenlabs/litiengine/util/ColorHelperTests.java
Outdated
Show resolved
Hide resolved
litiengine/src/test/java/de/gurkenlabs/litiengine/util/ColorHelperTests.java
Outdated
Show resolved
Hide resolved
litiengine/src/test/java/de/gurkenlabs/litiengine/util/ColorHelperTests.java
Outdated
Show resolved
Hide resolved
This makes it easier to understand which parameter goes to corresponds with which byte in the red200 variable.
@Gamebuster19901 thank you for your review! All your suggestions make sense. I have tried to implement all your suggestions. Hopefully I have succeeded. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot, both @Josef-Friedrich and @Gamebuster19901 :)
This prevents the variables and their value assignments from having to be repeated four times.
Instead of
DRY Don’t repeat yourself ->