IntelliJ IDEA 2018.1 EAP: editor enhancements and more

We’ve just rolled out a new IntelliJ IDEA 2018.1 EAP build. This time it’s all about editor enhancements, improvements in the VCS, and new and updated inspections. To try the latest EAP build right away download it from our our website or update to it via Toolbox App.

With IntelliJ IDEA by collapsing some, of the currently unnecessary blocks or code regions you can get a good overview of your code. Although up until now if a collapsed block contained some errors or warnings, the IDE would display notifications as colored stripes only visible in the scroll bar. These notifications are easy to miss, and they don’t provide any information about where exactly in your code the problem exists.

The upcoming IntelliJ IDEA 2018.1 highlights the folded code regions that contain errors or warnings, and colors such blocks according to their validation status. This give you the ability to quickly find the problem in your code.


Also, when you search through the current file the IDE now highlights the folded code regions if they contain the matching occurrences.


Version Control Systems

For the upcoming IntelliJ IDEA 2018.1 we’ve redesigned the Commit combo-button of the Commit Changes dialog to make it more user-friendly. In addition to this, now after you evoke the Commit Changes dialog you can perform the Commit and Push… action using the new shortcut: Alt + Cmd +K (macOS) or Alt + Ctrl + K (Windows and Linux).



In other news, now the IDE detects an explicitly redundant close() call of the resource at the end of a try-with-resources block.


We’ve updated the compute constant value intention, and we have now made it into an inspection, so now it can be applied to the entire file. This inspection is called: Constant expression can be evaluated. The IDE now lets you preview the result of the replacement in a quick-fix name. By the way, the Constant expression can be evaluated inspection now determines the value of the String concatenation.


Last but not least, the mismatched query and update of collection inspection have been updated, with fixes for several minor issues. But if you still encounter any issues, please report them.

A complete list of the changes has been posted here.

Download and try these new features for yourself! Don’t forget to get back to us with your improvement suggestions, and bug reports, they can all be submitted to our issue tracker.

Happy Developing!

About Zlata Kalyuzhnaya

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

16 Responses to IntelliJ IDEA 2018.1 EAP: editor enhancements and more

  1. ADEV says:

    If you need more suggestion to improve the editor:

    – split run panel so we can see two output (client/server)
    – fold/collapse if/while/else/for etc
    – dlang support

  2. Leif says:

    +1 for – fold/collapse if/while/else/for etc

  3. Rik says:

    Why is this bug still open while you claim you have made the Commit Changes dialog more user-friendly?

    • Dmitriy Smirnov says:

      We fixed it in a different way. Now there are dedicated shortcuts.
      For commit and push – Alt+Cmd/Ctrl+K
      To open the drop-down list – Alt+Shift+Enter.
      Ctrl+Enter executes Commit, this has not changed.

      Note that the Commit button and the Expand drop-down list are two separate buttons, and Alt+I should not open a drop-down, cause it is the accelerator for Commit. Thus calling it executes commit, and it is expected.

      The issue is that it also adds an unexpected symbol to the commit message. It happens on Mac only though, because Alt+smth are used to input special symbols there, and it is not specific to the commit dialog.

  4. wang says:

    why when i use ” or
    ” or

    in XXXMapper.xml come to error

    Doesn’t support mybatis?

    • wang says:

      sql id=”Base_Column_List”

      include refid=”Base_Column_List”

      trim prefix=”(” suffix=”)” suffixOverrides=”,”

      doesn’t work

  5. macdevign says:

    Will be great if this release is set to fix JShell Console issues. Useful as it seems, it is basically not usable with many critical bugs (eg compilation fail, auto-complete issues ). Not too sure why it didn’t receive as much attention.

    • says:

      Hi macdevign. Currently we’re not sure how useful and popular Jhell is. It seems that user already can get not less using Scratches functionality, which is already stable. Please let us know if you have some specific use cases for JShell which cannot be done with Scratches.

      • macdevign says:

        I find that JShell Console is really useful for quickly experimenting with of Java and third party library, just like Ruby IRB, without those Java formalities still require by Scratch functionality (class structure, with main. can we even run Scratch file ? ). Probably take time for Java developers to realize how JShell can be useful as Java 9 is still pretty recent.

        I will have use JShell from Java9 if not for its less than friendly auto-completion and quirky editing feature.

    • Brice says:

      Try the groovy console it has been there since years, and it allows to play with the compiled classes of the module of your choice.

      • macdevign says:

        Unfortunately Groovy is not 100% Java (eg syntax). People just want to copy some fragment of Java code from net and run-test it quick, without rewriting it.

  6. Cris says:

    I see now (not sure if it started with this EAP when you change between light/dark editor schemes, IntelliJ pops up a dialogue to also switch the UI theme similarly.

    Is there a setting for this? I accidentally declined, but would like this behaviour for future scheme changes.

  7. John Ruffo says:

    It would be great if it had profiling tool out of the box, like NetBeans.

    • Dmitry says:

      I noticed a Profile button replaced Run with Coverage on the main toolbar in a fresh IDEA setup.
      It does not seem to do anything “out of the box”. But probably it’s a hint for a built-in profiler?

Leave a Reply

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