diff --git a/docs/images/multiplatform/multiplatform-hierarchy-completion.gif b/docs/images/multiplatform/multiplatform-hierarchy-completion.gif new file mode 100644 index 00000000000..c6cd4cfef0c Binary files /dev/null and b/docs/images/multiplatform/multiplatform-hierarchy-completion.gif differ diff --git a/docs/images/multiplatform/multiplatform-hierarchy-completion.png b/docs/images/multiplatform/multiplatform-hierarchy-completion.png new file mode 100644 index 00000000000..9a5f253c6fe Binary files /dev/null and b/docs/images/multiplatform/multiplatform-hierarchy-completion.png differ diff --git a/docs/topics/whatsnew-eap.md b/docs/topics/whatsnew-eap.md index 2b91589da46..2989586374d 100644 --- a/docs/topics/whatsnew-eap.md +++ b/docs/topics/whatsnew-eap.md @@ -109,7 +109,7 @@ Green source sets are actually created and present in the project, while gray on To make it easier to work with the created project structure, IntelliJ IDEA now provides completion for source sets created with the default hierarchy template: -![The IDE completion for source sets names](multiplatform-hierarchy-completion.gif){width=700} +IDE completion for source set names Kotlin also warns you if you attempt to access a source set which doesn't exist because you haven't declared the respective target. In the example below, there is no JVM target (only `androidTarget`, which is not the same). But let's try to access the `jvmMain` source set