Discover Intellij IDEA for Scala

Install Scala plugin

To start working with Scala in IntelliJ IDEA you need to download and enable the Scala plugin. If you run IntelliJ IDEA for the first time, you can install the Scala plugin when IntelliJ IDEA suggests you to download featured plugins. Otherwise, you can use the Plugins page for the installation.

After the installation, IntelliJ IDEA will keep track of the plugin updates and will suggest you to update the plugin when a new version is available. You can also use the Plugin update channel at the Updates tab, located in Settings | Languages & Frameworks | Scala to check for Scala nightly, EAP, or release builds.

Now you can successfully check out from VCS, create, or import Scala projects.

User interface

The user interface for Scala looks similar to a regular one unless you work with SBT projects, in that case the SBT projects tool window and SBT Shell become available.

Also IntelliJ IDEA lets you keep track of error analysis based on the Scala type system using the Scala type-aware highlighting. By default, it is enabled and you can see the icon located at the bottom of the user interface. You can click the icon or press Ctrl+Shift+Alt+E to disable this feature.

The most interesting part of the user interface is the IntelliJ IDEA Editor since it lets you invoke almost any IDE feature without leaving it, which helps you organize a layout where you have more screen space because auxiliary controls like toolbars and windows are hidden.

Accessing a tool window via its shortcut moves the input focus to it, so you can use all keyboard commands in its context. When you need to go back to the editor, pressEscape.

Below is a list of shortcuts that invoke the tool windows you will most often need:

The SBT projects tool window and SBT Shell can be accessed via main menu (View | Tool Windows) or you can always press Ctrl+Shift+A to quickly search for these items.

When you want to focus on the code, try the Distraction Free Mode. It removes all toolbars, tool windows, and editor tabs. To switch to this mode, on the main menu select View | Enter Distraction Free Mode.

An alternative to the Distraction Free Mode may be hiding all tool windows by pressing Ctrl+Shift+F12. You can restore the layout to its default by pressing this shortcut once again.

The Navigation Bar is a compact alternative to the Project Tool Window. To access the Navigation Bar, press Alt+Home.

Most components in IntelliJ IDEA (both tool windows and pop-ups) provide speed search. This feature allows you to filter a list, or navigate to a particular item by using a search query.

For more details, refer to Guided Tour around the User Interface, Editor basics, and Working with Tool Windows.

Editor basics

Since in IntelliJ IDEA you can undo refactorings and revert changes from Local History, it makes no sense to ask you to save your changes every time.

The most useful Editor shortcuts are:

To expand a selection based on grammar, pressCtrl+W. To shrink it, press Ctrl+Shift+W.

IntelliJ IDEA can select more than one piece of code at a time. You can select next occurrence via Alt+J and deselect by pressing Shift+Alt+J. You can even select all occurrences at once, by pressing Ctrl+Shift+Alt+J.

For more details, refer to Editor basics.

Code completion

When you access Basic Completion by pressing Ctrl+Space, you get basic suggestions for variables, types, methods, expressions, for a parameter name you get type suggestions and so on. When you call Basic Completion twice, it shows you more results, including methods from implicit conversions that you can import.

The Smart Completion feature is aware of the expected type and data flow, and offers the options relevant to the context. To call Smart Completion, press Ctrl+Shift+Space. When you call Smart Completion twice, it shows you more results, including chains.

To let IntelliJ IDEA complete a statement for you, pressN/A. Statement Completion will automatically add the missing parentheses, brackets, braces and the necessary formatting.

If you want to see the suggested parameters for any method or constructor, press Ctrl+P. IntelliJ IDEA shows the parameter info for each overloaded method or constructor, and highlights the best match for the parameters already typed.

The Postfix Completion feature lets you transform an already typed expression to another one, based on the postfix you type after a dot.

For more details, refer to Auto-Completing Code.

Navigation

Navigation shortcuts include:

For more details, refer to Navigating Through the Source Code.

Quick pop-ups

Quick Pop-ups are helpful for checking additional information related to the symbol at the caret. Below is a list of pop-ups you should know if you want to be more productive:

Refactoring basics

IntelliJ IDEA offers a comprehensive set of automated code refactorings that lead to significant productivity gains when used correctly. Firstly, don't bother selecting anything before you apply a refactoring. IntelliJ IDEA is smart enough to figure out what statement you're going to refactor, and only asks for confirmation if several choices are possible.

For extracting a trait, use main menu (Refactor | Extract | Trait).

For more details, refer to Refactoring Source Code.

Finding usages

Find Usages helps you quickly find all pieces of code referencing the symbol at the caret (cursor), no matter if the symbol is a class, method, field, parameter, or another statement. Just press Alt+F7 and get a list of references grouped by usage type, module, and file.

If you want to set custom options for the Find Usages algorithm, press Ctrl+Shift+Alt+F7, or click the first button on the right panel with search results.

If what you're looking for is plain text, use Find in Path by pressing Ctrl+Shift+F.

For more details, refer to Finding Usages.

Inspections

Inspections are built-in static code analysis tools that help you find probable bugs, locate dead code, detect performance issues, and improve the overall code structure.

Most inspections not only tell you where a problem is, but also provide quick fixes to deal with it right away. Press Alt+Enter to choose a quick fix.

Inspections that are too complex to be run on-the-fly are available when you perform code analysis for the entire project. You can do this in one of the following two ways: by selecting Analyze | Inspect Code from the main menu, or by selecting Analyze | Run Inspection by Name to run an inspection by its name.

Note that while inspections provide quick-fixes for code that has potential problems, intentions help you apply automatic changes to code that is correct. To get a list of intentions applicable to the code at the caret, pressAlt+Enter.

For more details, refer to Code Inspection.

Code style and formatting

IntelliJ IDEA automatically applies a code style you've configured in the Code Style settings as you edit, and in most cases you don't need to call the Reformat Code action explicitly.

Useful formatting shortcuts:

You can also use the Scalastyle inspection for checking your Scala code. Simply place scalastyle_config.xml in the <root>/.idea or <root>/project directory and inspect your code.

Note that by default, IntelliJ IDEA uses regular spaces for indents instead of tabs. If you have files with lots of indents, you may want to optimize their size by enabling the Use tab character option located in Settings | Editor | Code Style | Scala.

For more details, refer to Reformatting Source Code.

Run and debug

Once you've created a Run/Debug configuration by selecting Run | Edit Configurations from the main menu, you are able to run and debug your Scala code.

For SBT projects you are also able to run and debug your code using SBT shell. Options Use SBT shell for build and import and Enable debugging for SBT shell, located on SBT page in settings, will enable you to do so.

For quick code evaluation, you can use a Scala worksheet that enables you to interactively run your code. Press Ctrl+Shift+Alt+X to create a light version of the Scala worksheet and Ctrl+Alt+W to run it.

The regular actions for run/debug are as follows:

When in the debug mode, you can evaluate any expression by using the Evaluate expression tool, which is accessed by pressing Alt+F8. This tool provides code completion in the same way as in the editor, so it's easy to enter any expression.

Sometimes, you may want to step into a particular method, but not the first one which will be invoked. In this case, use Smart step into by pressing Shift+F7 to choose a particular method.

If you want to "rewind" while debugging, you can do it via the Drop Frame action. This is particularly helpful if you mistakenly stepped too far. This will no revert the global state of your application, but will at least let you revert to a previous stack frame.

For more details, refer to Running and Debugging.

Build

When you've imported or created your SBT project, you can edit its build.sbt file directly in the editor. In build.sbt you can specify compiler options, information about your sub-projects, and also define your tasks and settings. Every time you change the build.sbt file, you need to synchronize your changes with the project model in IntelliJ IDEA.

You can select the Use Auto-import option to synchronize the changes made to build.sbt automatically. To access this option, select File | Settings | Build, Execution, Deployment | Build Tools | SBT.

For manual synchronization, use the corresponding action on the SBT projects tool window toolbar: .

Note that any SBT task can be attached to be run before a run configuration.

IntelliJ IDEA also lets you use other build tools such as Gradle or Maven to build your Scala project.