Open Intybyte opened 2 months ago
Pro Tip! You can help us label your Pull Requests by using the following branch naming convention next time you create a pull request. โค๏ธ Branch naming convention | Label |
---|---|
feature/** |
๐ Feature |
fix/** |
โจ Fix |
chore/** |
๐งน Chores |
api/** |
๐ง API |
performance/** |
๐ก Performance Optimization |
compatibility/** |
๐ค Compatibility |
If your changes do not fall into any of these categories, don't worry. You can just ignore this message in that case! ๐
Thanks for your first PR thank you for reviewing it.
Does this cover all of the soundservice?
A Slimefun preview build is available for testing! Commit: 03aa31c8
https://preview-builds.walshy.dev/download/Slimefun/4180/03aa31c8
Note: This is not a supported build and is only here for the purposes of testing. Do not run this on a live server and do not report bugs anywhere but this PR!
Does this cover all of the soundservice?
It should, I get all the element in theSoundEffect
enum and check if it has a configuration using the SoundService
, as it might be null even if it should not.
In fact the SoundEffect
enum has a method that gets the SoundService
instance in order to check it, which before returning the value checks if it is null
, and prints a warning (the comment itself says that this should not happen in the first place), so by adding this test you are checking all of the elements of SoundEffect
ahead in the testing.
It is complete unless the reload
method requires some testing too.
Description
Unit tests for new sound system
Proposed changes
Adding unitest
Related Issues (if applicable)
Resolves #3881, #2844, #3880
Checklist
Nonnull
andNullable
annotations to my methods to indicate their behaviour for null values