From 188602fc1f113038c580fd56c8d3a90890a3e50e Mon Sep 17 00:00:00 2001 From: Dmitrii Gridin Date: Mon, 30 Sep 2024 15:52:09 +0200 Subject: [PATCH] Declaring-K2-Compatibility.md: clarification Clarify why it is recommended to declare `supportsKotlinPluginMode` even if a plugin is in the whitelist --- Writerside/topics/Declaring-K2-Compatibility.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Writerside/topics/Declaring-K2-Compatibility.md b/Writerside/topics/Declaring-K2-Compatibility.md index a716102..6a81b7f 100644 --- a/Writerside/topics/Declaring-K2-Compatibility.md +++ b/Writerside/topics/Declaring-K2-Compatibility.md @@ -31,5 +31,6 @@ To test it locally when using the [IntelliJ Platform Gradle Plugin](https://plug A number of third-party plugins may already be enabled in the K2 mode without a `supportsK2` declaration. The IntelliJ Kotlin plugin keeps an [internal list](https://github.com/JetBrains/intellij-community/blob/master/platform/core-impl/resources/pluginsCompatibleWithK2Mode.txt) of plugins which are known to be compatible with the K2 mode as they do not use Kotlin analysis. The authors of these -plugins should not be surprised if their plugin already works in the K2 mode. However, it's still advised to declare K2 -support explicitly. \ No newline at end of file +plugins should not be surprised if their plugin already works in the K2 mode. However, it's still advised to check and +declare K2 support explicitly as this list is not future-proof and could potentially contain unsafe plugins due to some +circumstances. \ No newline at end of file