Skip to content
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

Add support for IJ 241, drop 221 #507

Merged
merged 1 commit into from Feb 6, 2024
Merged

Conversation

rock3r
Copy link
Contributor

@rock3r rock3r commented Feb 2, 2024

As per title, this PR adds support for IJ 241, which is currently throwing an error due to an action missing the update thread override. Concurrently, we had to drop support for 221 as that API isn't available until 222. We also removed one deprecated-as-error API usage by copy-pasting that function into the plugin (yeah... I know), and replaced a deprecated IJ Platform function usage with its Kotlin stdlib equivalent.

Include updating Gradle to 8.5 and Gradle IJ plugin to 1.17.0; the verifier now runs on all latest supported versions of the IJ Platform. Smoke tested on 222 and 241 EAP 3.

I took the liberty of creating a changelog entry for 2.4.0

Include updating Gradle to 8.5 and Gradle IJ plugin to 1.17.0
@schalkms
Copy link
Member

schalkms commented Feb 6, 2024

Thanks for the tremendous help!!

@cortinico cortinico merged commit da31ec7 into detekt:main Feb 6, 2024
3 checks passed
@rock3r rock3r deleted the support-241 branch February 7, 2024 09:01
@@ -57,7 +57,7 @@ class RulesBrowserService : Disposable {
}

private fun updateStyles() {
val ideTheme = if (StartupUiUtil.isUnderDarcula()) "dark" else "light"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, is it internal in future IJ versions than 222?

Screenshot from 2024-03-31 10-11-40

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't look like from the screenshot... But worst case scenario you can use JBColor.isBright()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants