Hi all. It seems the SQLDelight IntelliJ plugin is...
# squarelibraries
c
Hi all. It seems the SQLDelight IntelliJ plugin is not compatible with the latest versions of IntelliJ: what version/edition of IntelliJ are y'all using? And is every SQLDelight user using the plugin, or do some have other workflows?
l
Thanks to the 2.1.0 release that was released last week, for the first time in a long time the stable version is running flawlessly for my team (SQLDelight + plugin 2.1.0 with IntelliJ 2025.1.1.1). What issues have you been running into? If you're running snapshot/EAP plugin builds try switching to the new stable version. It took a few steps for us: remove the EAP repo setup (basically the opposite of these instructions), uninstall the plugin, and then reinstall 2.1.0 from the IntelliJ Plugin Marketplace.
👍 1
j
I too am seeing compatibility issues with v2.1.0 on AS Meerkat Feature Drop | 2024.3.2. I am no longer seeing the "hanging sync error" issue as described here: https://github.com/sqldelight/sqldelight/issues/5664. However, 1. There is an "Analyzing..." prompt in the upper right corner of the source file pane that never goes away; yet, clicking on it reveals nothing in the IDE dialogs/panes to suggest that some work is actually being done 2. I cannot edit a .sq file; the IDE makes it read-only or something. when attempting to edit, a dialog pops up with a title of "IDE error occurred" with a hyperlink subtitle "See details and submit report". Clicking on the hyperlink appears to do nothing. 3. When I look in idea.log, I keep seeing "Exception in thread "DefaultDispatcher-worker-19" java.lang.NoSuchMethodError: 'java.util.stream.Stream com.intellij.openapi.extensions.ExtensionPoint.extensions()'" suggesting that https://github.com/sqldelight/sqldelight/issues/5310 should be re-opened as not fixed? @jw thoughts on re-opening that issue or would you prefer I file another?
😭 1
idea.log snippet
h
Unfortunately, I can reproduce it on IntelliJ idea 2025.1.1 too
👀 1
Don’t know if 5310 is the same issue or there should be a new issue. Anyway, the plugin is broken again.
😭 1