tools/idea-plugin/src/main/kotlin/io/github/composegears/valkyrie/completion/ImageVectorIcon.kt (1)

71-81: ⚡ Quick win

Consider a more generic exception message.

The warning message assumes "invalid path data" but the caught exception could be due to other causes (e.g., memory issues, internal VdPreview failures, thread interruption). While "invalid path data" is accurate for the primary use case from issue #1004, a more generic message would be safer.

💬 Suggested improvement

         } catch (e: Exception) {
             Logger.getInstance(ImageVectorIcon::class.java)
-                .warn("Failed to render icon preview (invalid path data): ${e.message}")
+                .warn("Failed to render icon preview: ${e.message}")
             return null
         }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@tools/idea-plugin/src/main/kotlin/io/github/composegears/valkyrie/completion/ImageVectorIcon.kt`
around lines 71 - 81, The catch block in ImageVectorIcon around
VdPreview.getPreviewFromVectorXml currently logs a specific "invalid path data"
message; change it to a more generic warning that does not assume the root cause
and include the caught exception details (e.message and/or e::class.simpleName)
for context. Update the Logger.getInstance(ImageVectorIcon::class.java).warn
call to a neutral message like "Failed to render icon preview" and append the
exception type and message from the caught Exception to help debugging while
avoiding incorrect assumptions about the error source.