Refactor resource bundle method and update class instances. #27

Sign in to view logs

GitHub Actions / Qodana for JVM completed Mar 29, 2024 in 0s

54 new problems found by Qodana for JVM

Qodana for JVM

54 new problems were found

Inspection name	Severity	Problems
`Call to 'printStackTrace()'`	🔶 Warning	25
`Unused import`	🔶 Warning	12
`Unused assignment`	🔶 Warning	10
`AutoCloseable used without 'try'-with-resources`	🔶 Warning	4
`Mismatched read and write of array`	🔶 Warning	1
`Duplicated code fragment`	◽️ Notice	2

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

Or via our issue tracker: https://jb.gg/qodana-issue
Or share your feedback: https://jb.gg/qodana-discussions

Details

This result was published with Qodana GitHub Action

Annotations

Check warning on line 73 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

AutoCloseable used without 'try'-with-resources

'FileOutputStream' used without 'try'-with-resources statement

Check warning on line 118 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

AutoCloseable used without 'try'-with-resources

'FileOutputStream' used without 'try'-with-resources statement

Check warning on line 170 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

AutoCloseable used without 'try'-with-resources

'FileInputStream' used without 'try'-with-resources statement

Check warning on line 190 in src/main/java/com/severalcircles/flames/Flames.java

github-actions / Qodana for JVM

AutoCloseable used without 'try'-with-resources

'FileWriter' used without 'try'-with-resources statement

Check notice on line 62 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

Duplicated code fragment

Duplicated code

Check notice on line 184 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

Duplicated code fragment

Duplicated code

Check warning on line 312 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

Mismatched read and write of array

Contents of array `newChannelWords` are written to, but never read

Check warning on line 32 in src/main/java/com/severalcircles/flames/frontend/thanks/ThanksCommand.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 74 in src/main/java/com/severalcircles/flames/util/StringUtil.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 55 in src/main/java/com/severalcircles/flames/frontend/thanks/ThanksEmbed.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 194 in src/main/java/com/severalcircles/flames/Flames.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 35 in src/main/java/com/severalcircles/flames/frontend/thanks/ThanksContext.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 45 in src/main/java/com/severalcircles/flames/frontend/data/user/LocaleCommand.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 124 in src/main/java/com/severalcircles/flames/Flames.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 33 in src/main/java/com/severalcircles/flames/events/SelectMenuEvent.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 36 in src/main/java/com/severalcircles/flames/events/SelectMenuEvent.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 95 in src/main/java/com/severalcircles/flames/events/MessageEvent.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 50 in src/main/java/com/severalcircles/flames/data/FlamesDataManager.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 33 in src/main/java/com/severalcircles/flames/frontend/data/user/embed/GetAlongEmbed.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 64 in src/main/java/com/severalcircles/flames/exception/FlamesHandlerEmbed.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 26 in src/main/java/com/severalcircles/flames/frontend/data/user/GetAlongCommand.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 57 in src/main/java/com/severalcircles/flames/frontend/conversations/ConversationEmbed.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 33 in src/main/java/com/severalcircles/flames/frontend/data/user/UserContextData.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 21 in src/main/java/com/severalcircles/flames/exception/handle/ExceptionHandler.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

Check warning on line 161 in src/main/java/com/severalcircles/flames/conversations/Conversation.java

github-actions / Qodana for JVM

Call to 'printStackTrace()'

Call to `printStackTrace()` should probably be replaced with more robust logging

View more details on GitHub Actions