{"id":227249,"date":"2019-11-15T09:00:09","date_gmt":"2019-11-15T17:00:09","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/java\/?p=227249"},"modified":"2019-12-11T18:23:08","modified_gmt":"2019-12-12T02:23:08","slug":"java-on-visual-studio-code-november-update","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/java-on-visual-studio-code-november-update\/","title":{"rendered":"Java on Visual Studio Code November Update"},"content":{"rendered":"

Welcome to the November update of Java on Visual Studio Code. Starting this month, we’re moving to a new home called Java at Microsoft<\/a>, where you can find not only updates about Java on Visual Studio Code, but also other news and insights for Java development with other Microsoft tools, Azure services and OpenJDK. You can subscribe this blog by following @JavaAtMicrosoft.<\/p>\n

In this update, we’d like to share some improvements we’ve made for code editing experience, more code actions, Java 13 support for Gradle projects and new features in Test Runner and Checkstyle extensions.<\/p>\n

Code Editing<\/h3>\n
Provide better symbol details for the completion proposal<\/h5>\n

Originally, we only show javadoc for the auto completion proposal, with a simple header. To provide more detailed information and help you choose the right item, we’re now adding more detailed symbol info to the header, and hopefully helps you find the right choice faster.<\/p>\n

Compare the previous and new information available for field<\/p>\n

\"\"<\/p>\n

Method<\/p>\n

\"\"<\/p>\n

Type<\/p>\n

\"\"<\/p>\n

Package<\/p>\n

\"\"<\/p>\n

Report unused code as unnecessary<\/h5>\n

We’ve added faded effect to unused code. So now it’s easier for you to spot them.<\/p>\n

\"\"<\/p>\n

Code actions<\/h3>\n

Add ‘final’ modifier where possible<\/h5>\n

In Java, there is a practice of declaring every variable (local or class), parameter final if they really are. If you like to apply this to you code, you will find this code action useful.<\/p>\n

\"\"<\/p>\n

Remove unnecessary cast<\/h5>\n

This code action will remove unnecessary cast in your code. (Note: the associated compiler warnings is not enabled by default. To enable this feature, you can manually append the compiler warning org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=warning<\/code> to the file .settings\/org.eclipse.jdt.core.prefs<\/code>)<\/p>\n

\"\"<\/p>\n

Other improvements<\/h3>\n
    \n
  1. Support Java 13 for Gradle project. Gradle 6.x projects with Java 13 are now supported! We’ve also upgraded embedded maven version to 3.6.2 as well.<\/li>\n
  2. Expose Invert Condition<\/code> code action which automatically find the boolean expression around your caret so you don’t need to select the entire expression to trigger it.<\/li>\n
  3. Add text selection support in code snippet so after inserting certain code snippet, VS Code will select\/highlight certain code where you will likely to take action thereafter.<\/li>\n
  4. Java Test Runner<\/a> now supports module path for your modular Java project. It also added a new ‘CollapseAll’ button for you to easily collapse your test cases in test explorer.<\/li>\n
  5. Checkstyle for Java<\/a> added support for custom checkstyle modules. Now you can set any 3rd-party modules for checkstyle using its path. For example, after using the below configuration, you can add\u00a0<module name=\"SingleBreakOrContinueCheck\"\/><\/code>\u00a0or\u00a0<module name=\"com.github.sevntu.checkstyle.checks.naming.SingleBreakOrContinueCheck\"\/><\/code>\u00a0to\u00a0checkstyle.xml<\/code> to leverage those checks.<\/li>\n<\/ol>\n
    \"java.checkstyle.modules\": [\r\n    \"${workspaceFolder}\/src\/main\/resources\/sevntu-checks-1.35.0.jar\"\r\n]<\/pre>\n
    Sign up<\/h3>\n
    If you’d like to follow the latest of Java on VS Code, please provide your email with us using the form below. We will send out updates and tips every couple weeks and invite you to test our unreleased feature and provide feedback early on.<\/p>\n
    <\/div>\n