You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enabling proper code generation for comments (Comment with Line/Block Comment) (#3582)
* feat: enabling proper code generation for comments (toggleable, Comment with Line/Block Comment)
* Add the correct ERL and elixir arguments for starting IEx depending on the version of elixir sdk
* Bundle latest OtpErlang.jar from JInterface v1.14 for OTP v26
* Infer OTP_RELEASE & ERLANG_SDK_HOME if no environment variable is set (#3600)
* Add compatibility for 2024.1 IDEs (#3569)
* Update gradlewrapper to v7.6.4
./gradlew wrapper --gradle-version=7.6.4
To fix gradle issue: gradle/gradle#27156
* Remove use of `FileUtil.FILE_HASHING_STRATEGY` from Intellij FileUtil, 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
* Add support for 2024.1 IDEs (and runs tests correctly against 2024.1)
* Update usages group wording for 2024.1
* Fix more sdk configuration commits in application RW thread, fixes compatibility with IDEs v2024.1
* Fix whitespace in tests due to 2024.1 change
I believe 2024.1 changed how the Usages work.
In 2023.x:
```kotlin
val usages =
myFixture.testFindUsagesUsingAction("module_attribute_usage.ex",
"kernel.ex")
.map { it as UsageInfo2UsageAdapter }
```
In the debugger shows:
```
0 = {ReadWriteAccessUsageInfo2UsageAdapter@19239} "4|def usage, |do|:
|@|module_attribute"
1 = {ReadWriteAccessUsageInfo2UsageAdapter@19240} "2|@|module_attribute|
|1"
```
For 2024.1, this shows:
```
0 = {ReadWriteAccessUsageInfo2UsageAdapter@19421} "2|
|@module_attribute| 1"
1 = {ReadWriteAccessUsageInfo2UsageAdapter@19422} "4| def usage, do:
|@module_attribute"
```
I believe it not shows the whitespace for the file, where previously it
didn't.
* pin versions
* use BasePlatformTestCase to stop warning
* add do block match test
* set 241.0 as the version, to fix certain intellij warnings
* fix key
* revert tests
* use thread
---------
Co-authored-by: Josh Taylor <joshuataylorx@gmail.com>
* Add 18.0.0 changelog, fix version (#3602)
* support only the newest version.
* remove tests for now, kind of pointless
---------
Co-authored-by: Ashley Sommer <ashleysommer@gmail.com>
Co-authored-by: Josh Taylor <joshuataylorx@gmail.com>
0 commit comments