Add comptibility for 2024.1 IDEs #3569
Conversation
./gradlew wrapper --gradle-version=7.6.4 To fix gradle issue: gradle/gradle#27156
…, it was removed in 2024.1. (Note, this is only used in the jps-build test suite). This also removes references to Trove THashSet, and no longer stores File directly in sets or collections. See JetBrains/intellij-community@560e8fc
…mpatibility with IDEs v2024.1
|
Thanks for doing this. Would it be helpful if we try out the plugin? If you attach the plugin I'd be happy to install it and give it a go, so we can help boost the confidence that the plugin works as advertised? |
|
@gaggle Yes, I had the same thought. I'll finish my current round of testing, and later today I'll attach the .zip for users to try. |
|
hi @ashleysommer having an issue with the plugin where some coloring seems off and when i tried adding a moduledoc, the |
Yeah, there's probably a bunch of things still not working correctly. I'm actually very new to Elixir, I'm still learning what the features are and I was only using this plugin for 1 week before Jetbrains 2024.1 IDEs were released, and I'm still learning what this plugin is even capable of or what it should do correctly. |
|
It LGTM too! |
| @@ -82,7 +82,7 @@ allprojects { | |||
| } | |||
|
|
|||
| runPluginVerifier { | |||
| ideVersions = ["2023.3"] | |||
There was a problem hiding this comment.
Based on previous compatibility PRs we normally drop support for the previous version, so this should probably just be ["2024.1"]
There was a problem hiding this comment.
The old version is only dropped if a required code change makes it impossible to build for both versions. It's a coincidence that that has been the case for recent one.
There was a problem hiding this comment.
Gotcha, thanks for the clarification!
There was a problem hiding this comment.
The commit I used for reference was this one: 876b770
That does simply add the new version to the list, as I've done here.
| @@ -70,7 +70,7 @@ allprojects { | |||
| pluginDescription.set(bodyInnerHTML("resources/META-INF/description.html")) | |||
|
|
|||
| sinceBuild = "233.11799.241" | |||
| untilBuild = "233.*" | |||
| untilBuild = "241.*" | |||
There was a problem hiding this comment.
Based on previous compatibility PRs sinceBuild typically matches untilBuild since we're dropping support for previous versions.
There was a problem hiding this comment.
I haven't seen any compatibility PRs in this repo where the sinceBuild matches the untilBuild, that doesn't seem right.
There was a problem hiding this comment.
Would this be the reason why it's showing this "super friendly" warning? I'm not too across how versioning works with plugins yet, so unsure if this would also need to be tweaked 🤔
> Task :verifyPluginConfiguration
[gradle-intellij-plugin :verifyPluginConfiguration] The following plugin configuration issues were found:
- The 'since-build' property is lower than the target IntelliJ Platform major version: 233.11799.241 < 241.
| @@ -8,7 +8,7 @@ jobs: | |||
|
|
|||
| strategy: | |||
| matrix: | |||
| ideaVersion: [ "2023.3" ] | |||
| ideaVersion: [ "2023.3", "2024.1" ] | |||
There was a problem hiding this comment.
Pretty sure this can just be ["2024.1"] since we normally just support the current version.
|
|
||
| @Override | ||
| public void logDeletedFiles(Collection<String> paths) { | ||
| for (String path:paths){ | ||
| myDeletedFiles.add(new File(path)); | ||
| myDeletedFiles.add(new File(path).getAbsolutePath()); |
There was a problem hiding this comment.
Is this a change in behavior? I'm not sure if path was previously absolute or relative (it looks relative).
There was a problem hiding this comment.
The change is the set is storing the string version of the file instead of the File object. In the previous version, the handler was calling .getAbsolutePath() on every File object in the set, so we simply do that here instead and save a step.
| private fun usages(): String { | ||
| val ideVersion = Version.parseVersion(ApplicationInfoEx.getInstance().fullVersion) | ||
| val usagesString = if (ideVersion === null || ideVersion.lessThan(2021,2,0)) { | ||
| "Found usages" | ||
| } else { | ||
| } else if (ideVersion.lessThan(2024,1,0)) { | ||
| "Usages in" | ||
| } else { | ||
| "Usages" | ||
| } | ||
| return usagesString | ||
| } |
There was a problem hiding this comment.
I'm not sure I understand what's driving this change. Can you walk me through it please?
There was a problem hiding this comment.
This is to help some tests pass.
In February, IntelliJ changed the wording of the text representation of the find usages response. That change made its way into all 2024.1 IDEs and broke these tests.
JetBrains/intellij-community@0706bea
Note, there are still some other changes in 2024.1 that are preventing these tests from actually passing, but this is the simple first step to remedy the bulk of the error messages.
There was a problem hiding this comment.
Is it necessary to support previous build versions if we are bocking these versions with the from-version attribute?
There was a problem hiding this comment.
Good point, we really don't need the case to handle the pre-2021.2 usages string.
It had been in the plugin code right up to and including the 2023.3 release, thats why I left it in there in this change, but refactoring it like this could be a good opportunity to remove that old version compatibility.
|
Thanks for looking at this! Note that while it does allow the plugin to load I am seeing various UI issues with intellij-elixir-17.0.0-pre+20240408035552.zip. Most annoyingly I have lost the matching brackets highlight - you don't realise how much you use that until it is gone! Also comments are showing as black, the same as normal code, which is getting very confusing.
Is anyone seeing either of those issues? Edit - also we seem to have lost the ability to run tests via the IDE |
|
This worked fine for me with just updating until-version. I also played with changing org.jetbrains. I did need to purge m2 deps however. #3579 |
|
@ashleysommer @KronicDeth I have a commit in my fork that I believe fixes the failing I could use some feedback on this; I think the difference is just formatting for the usage output, in which case this commit should be good. I'm also still seeing the following test failures: These pass for me locally on the main branch and fail on @ashleysommer's branch, so I don't believe it is simply my environment setup. |
Yes, that is the main remaining test failure that I've been working to fix the last couple of weeks. I've been working on a way that can assert success of the tests regardless of the whitespace formatting in the returned usages serialization.
I don't see any of those |
I think I've narrowed down where this issue is coming from. I've found one difference in the parser in 2024.1 regarding brackets that must be causing this. |
Is this needed? From what I remember recent updates of this plugin required an upgrade of the IDE. |
I wouldn't know, I only started using this plugin in March 2024, after IntelliJ 2023.3 was released. Looking back through the upgrade commits, it seems like sometimes the min version is bumped, sometimes it isn't.
Well, no its not strictly needed, but all other changes in this branch have kept backwards compatibility with 2023.3 IDE, normally when I contribute to an open source project the expectation is to avoid breaking changes at all costs wherever possible. |
I have tested your build and it was not working with the newest IDEA, but it does work with the previous one making IEx and debugging work in the IDE with Elixir 1.16 and Erlang OTP 26. This is very helpful - thanks! Looking forward to seeing those in the next release. |
That binary you shared installs pretty well on my IntelliJ IDEA 2024.1.1 (Ultimate Edition) Build #IU-241.15989.150, built on April 29, 2024 |
|
Hey guys, is there any ETA for this? |
It certainly works fine for me, across both an Intel Mac and an ARM Mac. I have IntelliJ Ultimate 2024.1.1 installed, with |
well, it "works", but found that like the auto complete of say parentheses etc are gone and the colors come and go if the syntax is "broken" which happens as you type character by character. |
|
per formatting issues. branch by abstraction. Just clone the formatting logic, add a toggle to switch between the new/old logic. Make it work for just the new ide version then start comparing the change diffs to make the new iteration backwards compatible. |
|
If you can hack that to work properly I can help with the switching logic. |
|
Hi, is there an estimated timeline for this? Would be great to have it. |
|
@KronicDeth could we please have some clarity on this PR? |
|
Could I just build this branch and have it work on Intellij, |
|
I also encourage everyone interested to visit
and try to poke Jetbrains. Without a visible community, they will never support Elixir. |
Alternative to #3567
There were a couple more changes required other than simply bumping the IntelliJ IDE version number.
When I try to build this plugin against 2024.1 IDEs and run the Test suite, I get the error
NoSuchFieldError: FILE_HASHING_STRATEGY. See relevant underlying IDE code changeWhile in the process of fixing that issue, I upgraded the
org.jetbrains.intellijgradle plugin tov1.17.3as recommended in the IntelliJ docs. Unfortunately that brings in some other gradle dependencies that require gradlev7.6.4minimum see here for details.So this PR bumps IDE version to "2024.1", adds that version to the test suite
PluginVerifiermatrix, fixes theNoSuchFieldErrorinjps-buildtests, bumpsorg.jetbrains.intellijgradle plugin tov1.17.3, and bumps gradlewrapper version tov7.6.4.