IntelliJ IDEA 2018.1 EAP: Kotlin 1.2.30

The new IntelliJ IDEA 2018.1 EAP is here! Among other improvements and bug-fixes, it updates the Kotlin plugin to version 1.2.30.

The updated Kotlin plugin has some new intention actions. Now, in the Project Tool Window you can paste a code fragment directly into a package, and the IDE will create a new Kotlin file with the pasted code.

2018-03-06 17_43_48

It also offers new intentions that convert the scoping function calls let and run into each other, as well as also into apply and vice versa.


In addition, data flow analysis now works for mixed Kotlin and Java codebases.

There are also new warnings of possible conflicts introduced by the Rename refactoring.

You can find more information about Kotlin 1.2.30 here. The full list of changes for this build is available in Release Notes.

Download, try and share your feedback with us in the discussion forum or on twitter. If you find a bug, please report it to our issue tracker. Thanks!

Happy developing!

About Zlata Kalyuzhnaya

IntelliJ IDEA Marketing Manager at JetBrains.
This entry was posted in EAP Releases and tagged , . Bookmark the permalink.

One Response to IntelliJ IDEA 2018.1 EAP: Kotlin 1.2.30

  1. opticyclic says:

    The fact that such a basic operation that has been available in the Java editor for such a long time highlights how much of a pain it is to work with Kotlin.
    So many things that work in Java don’t in Kotlin and it is not a Pleasure to Develop!

    Alt-Enter to implement an interface from a library tries (and fails) to implement it in the library instead of my source!
    Pasting a class reference doesn’t auto-import puts the fully qualified class name
    That FQN is often not recognised
    Moving classes to different packages doesn’t update other references
    Other refactoring (that I can’t remember the details of!) fails to complete properly

    This feels like when the Gradle plugin was announced 7 years ago and it still doesn’t have the same functionality as the Maven plugin.

Leave a Reply

Your email address will not be published. Required fields are marked *