We’ve improved the performance of Scala 3 highlighting when many implicit parameters are imported and are needed to parse the code, for example, when the Cats library is being used. Now you can use JVM/JS/Native code from shared sources – completion, navigation and code highlighting will work.Īnd the Find Usages action now searches for symbols in sbt files. On top of that, we improved support for sbt cross-built projects. You can now specify the sbt launcher’s parameters You can also specify the sbt launcher’s parameters in Settings/Preferences | Build, Execution, Deployment | Build Tools | sbt. With v2023.1, this dialog is now available for sbt projects, as well. When you have an empty module and want to create the root directory for the source code, you can use the New Directory dialog, which contains some helpful suggestions. The Scala plugin can now identify unused imports when you use compiler-based highlighting We’ve also fixed the auto-import action for Enums. The IDE can now identify unused imports if your project uses this option. Scala 3.3, however, introduced a new compiler option, -Wunused:imports. If you use compiler-based highlighting, until now all imports have been marked as used. The indentation of the extension method is carried over correctly It also supports braceless syntax in worksheets and correctly interprets indentation when you move extensions methods up and down in your code. IntelliJ IDEA can now desugar braceless Scala code properly, and it handles refactorings where the “fewer braces” feature is used. Maciej Gorywoda Improved support for braceless Scala syntax
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |