{"id":59793,"date":"2020-07-22T15:08:08","date_gmt":"2020-07-22T14:08:08","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=scala&p=59793"},"modified":"2023-09-04T17:30:55","modified_gmt":"2023-09-04T16:30:55","slug":"intellij-scala-plugin-2020-2-indentation-based-brace-handling","status":"publish","type":"scala","link":"https:\/\/blog.jetbrains.com\/ru\/scala\/2020\/07\/22\/intellij-scala-plugin-2020-2-indentation-based-brace-handling","title":{"rendered":"IntelliJ Scala Plugin 2020.2: Indentation-based Brace Handling"},"content":{"rendered":"

Because Scala is a curly-bracket language<\/a>, adding and removing curly braces<\/strong> is an integral part of Scala programmers’ everyday life. Those actions compound, so every improvement in this area matters. To understand the new advances<\/strong>, let us first take a take a look at it from historical perspective (or just watch this<\/a>).<\/p>\n

Before<\/h2>\n

At the beginning, there was no IDE assistance, so you had to tinker with curly braces manually<\/strong>:<\/p>\n


\nhttps:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-1.mp4<\/a><\/video><\/div>\n

Not only did this require more keystrokes, but the code was not valid for long. It was not good…<\/p>\n

But now, thanks to Editor | General | Smart Keys | Insert paired brackets<\/em>, IntelliJ IDEA can add a complementary brace<\/strong> automatically:<\/p>\n

https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-2.mp4<\/a><\/video><\/div>\n

However, you have to do this in advance<\/strong>, as it does not work for already existing code<\/strong>:<\/p>\n

https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-3.mp4<\/a><\/video><\/div>\n

In such cases, you are right back to square one.<\/p>\n

As a workaround, you could use the Add braces<\/em> quick fix<\/strong> (or select the expression and press {<\/code>):<\/p>\n

https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-3a.mp4<\/a><\/video><\/div>\n

But you have to know about these features in the first place, and it requires an explicit action<\/strong> on your part.<\/p>\n

Fortunately, in Scala plugin 2019.2 we have introduced<\/a> automatic handling of complementary braces (Editor | General | Smart Keys | Scala | Wrap single expression<\/em>):<\/p>\n

https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-4.mp4<\/a><\/video><\/div>\n

A complementary brace<\/strong> can be added and removed automatically, regardless of existing code<\/strong> in between. (By the way, we received a lot of overwhelmingly positive feedback for this supposedly small feature.) But you still had to add or remove a single brace<\/strong>… that is… until now.<\/p>\n

After<\/h2>\n

Now we have taken it even further \u2013 both braces<\/strong> can be added and removed automatically and on the fly based on code indents<\/strong>:<\/p>\n

https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-5.mp4<\/a><\/video><\/div>\n

With this, you can make use of significant indentation<\/em> while still keeping the braces, even in Scala 2.x. To take advantage of this feature, just don’t think about the braces<\/strong> and let the IDE do the work. And it’s not just a catchphrase – to use the new feature, you must not use the legacy ones: don’t add a pair of {}<\/code>, don’t invoke the "wrap" quick fix, and don’t insert an opening {<\/code> manually.<\/p>\n

<\/a>The plugin can correctly handle appending or inserting a new line, keywords, and so on (and if braces are not needed, you can either press Enter<\/em> twice or press Backspace<\/em> to delete the indent):<\/p>\n

https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2020\/07\/braces-6.mp4<\/a><\/video><\/div>\n

At the moment, the plugin doesn’t remove braces by default, but you can enable it in Editor | General | Smart Keys | Scala<\/em>.<\/p>\n

To try this now, select Nightly builds<\/em> as your Settings | Languages | Scala | Updates | Channel<\/em> (you can revert to a more stable build in the same way at any time). We\u2019re announcing this feature early, before the official release, in order to gather more information and polish off the rough edges. We need your feedback!<\/strong> Please report any bugs to YouTrack<\/a>. If you have any questions, feel free to ask them in our Gitter<\/a>.<\/p>\n","protected":false},"author":11,"featured_media":60011,"comment_status":"closed","ping_status":"closed","template":"","categories":[808,89,8058,6945],"tags":[6233,83,6234,225],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/scala\/59793"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/scala"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/types\/scala"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/comments?post=59793"}],"version-history":[{"count":1,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/scala\/59793\/revisions"}],"predecessor-version":[{"id":273093,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/scala\/59793\/revisions\/273093"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/media\/60011"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/media?parent=59793"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/categories?post=59793"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/tags?post=59793"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/ru\/wp-json\/wp\/v2\/cross-post-tag?post=59793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}