You are viewing a single comment's thread from:
RE: Minecolonies & Small Fixes and Features
Thank you for your contribution.
- I can see you add null checks and try to solve/fix the errors, but it is very dangerous, as you are explicitly hiding the errors. One better way would be to throw the exception and log it in upper application level.
- Some paramters to method could be replaced with interfaces, so that you can unit tests them later with mocking.
- public, static methods can be unit tested for example the
checkForListInInvAndRequestespecially you have made quite a lot of changes which need to be covered by tests.
Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.
To view those questions and the relevant answers related to your post, click here.
Need help? Chat with us on Discord.
Thanks for the evaluation.
Usually, we either add logging where we don't expect nulls to happen at all. In some places, where it can happen due to the code flow, we don't.
I agree with the unit testing part, but, this is not so easy since mocking Minecraft is not an easy part at all. When we extend our API we plan on improving the way we handle Minecraft libraries to make mocking much easier.
Thank you for your review, @justyy! Keep up the good work!