Closed jbubik closed 1 year ago
These are almost always going to be code style issues rather than anything else. Quelea was originally written when Java 6 was the latest release - Java has changed a lot since then, so some of the code inevitably doesn't conform to best practice styles of later versions. As an example:
"ComboBox is a raw type. References to generic type ComboBox
should be parameterized"
...reflects the fact that in Java 6, it was a raw type, and in Java 7+ it's parameterised - it's just never been updated (and updating it doesn't make any functional difference, it's just a code style thing.)
We occasionally pick up a few of them for people to address for Hacktoberfest, otherwise though tend to leave them be. If anyone wants to create a PR to address any then feel free, but it needs to be short, concise (no spaghetti PRs trying to fix everything at once!) and clear that there's no functional change / degradation.
Thanks for explanation. I will try to help with the resource leaks a bit. I am making myself comfortable in this project now. Later I would like to contribute some more. We use Quelea since 2016 and it's cool.
Hello devs, the IntelliCode analysis in Visual Studio Code shows various warnings for Quelea source code. Different kinds actually (unused variables, unused imports, unused fields, unused methods, dead code, resource leaks). I am a newbie into Java, so maybe I'm worried about something simple and harmless. Still it may help you somehow, so I post it here. I want to help, not be rude or offensive.
Below is a JSON array holding the results. I have no idea how to post it differently.