-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IntelliJ plugin breaks find usages on 2024.1 EAP #5069
Comments
Android Studio is now based on 2024.1 so this is breaking there, too. |
Same here, version 2.0.2 did not fix the issue |
Just wanted to add: I built the plugin from source and the problem was fixed apparently. Maybe the published plugin was not correct? |
this is a bug in the sqlite dialect and not the intellij plugin, in order for it to work you need to make sure the sqlite dialect is also set to 2.0.2 and then restart the IDE |
After updating 2.0.2 and making sure this is also set on the dialect, I had to do a clean build then invalidate caches and restart on the ide to fix this issue. |
(note i use sqldelight on android) I never set the sqlite dialect because I figured i would just want to use the sqlite version that ships with the android device? at this point since IJ and latest AS dont work with this plugin (this plugin just breaks random files so i basically cant use this plugin at all with newer IJ and AJ) it seems like setting a dialect is pretty much a requirement. maybe as a feature request we require a dialect to be selected? |
For Android projects the appropriate dialect version is selected automatically based on your minSdk. |
interesting. wonder why any version of koala just dies on me. uninstalling the plugin corrects the issue. |
SQLDelight Version
2.0.1
IDE Version
2024.1 EAP Beta 1
Dialect
SQLite
Describe the Bug
Initially reported here https://youtrack.jetbrains.com/issue/KTIJ-29038 - basically something within sqldelight crashes and this has such an effect that the general find usages is broken.
Stacktrace
The text was updated successfully, but these errors were encountered: