{"id":230384,"date":"2024-01-30T23:40:42","date_gmt":"2024-01-31T07:40:42","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/java\/?p=230384"},"modified":"2024-01-30T23:40:42","modified_gmt":"2024-01-31T07:40:42","slug":"java-on-visual-studio-code-update-january-2024","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/java\/java-on-visual-studio-code-update-january-2024\/","title":{"rendered":"Java on Visual Studio Code Update – January 2024"},"content":{"rendered":"

Hi everyone, welcome to the first update for Visual Studio Code for Java of 2024! We hope everyone had a refreshing break. In this blog we have some exciting updates for the new Test Coverage UX as well as reliability and general user experience updates, so let’s get started!<\/p>\n

Update of Java 21 Feature Support<\/strong><\/h3>\n

As shared in our roadmap blog post<\/a> last December, integrating JDK 21 support is a key focus in enhancing fundamental experience. Following its release, many efforts have been done to supports its features. We’re pleased to share our progress. Here’s a summary of the features we currently support and those still in progress.<\/p>\n

Current Status<\/strong> (List referenced from here<\/a>)<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
430:<\/td>\nString Templates (Preview)<\/a><\/td>\nSupported<\/strong><\/span><\/td>\n<\/tr>\n
431:<\/td>\nSequenced Collections<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
439:<\/td>\nGenerational ZGC<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
440:<\/td>\nRecord Patterns<\/a><\/td>\nSupported<\/strong><\/span><\/td>\n<\/tr>\n
441:<\/td>\nPattern Matching for switch<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
442:<\/td>\nForeign Function & Memory API (Third Preview)<\/a><\/td>\nSupported<\/strong><\/span><\/td>\n<\/tr>\n
443:<\/td>\nUnnamed Patterns and Variables (Preview)<\/a><\/td>\nWork In Progress<\/strong><\/span><\/td>\n<\/tr>\n
444:<\/td>\nVirtual Threads<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
445:<\/td>\nUnnamed Classes and Instance Main Methods (Preview)<\/a><\/td>\nWork In Progress<\/strong><\/span><\/td>\n<\/tr>\n
446:<\/td>\nScoped Values (Preview)<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
448:<\/td>\nVector API (Sixth Incubator)<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
449:<\/td>\nDeprecate the Windows 32-bit x86 Port for Removal<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
451:<\/td>\nPrepare to Disallow the Dynamic Loading of Agents<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
452:<\/td>\nKey Encapsulation Mechanism API<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n
453:<\/td>\nStructured Concurrency (Preview)<\/a><\/td>\nSupported<\/span><\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/blockquote>\n

We will continue to work on the remaining features and share an update again soon. For users who currently do not need features that are work in progress, you can already use JDK 21 in Visual Studio Code Java.<\/p>\n

Test Coverage UX Updates<\/strong><\/h3>\n

In our previous blog, we shared the new Test Coverage feature<\/a> that can already be used in Visual Studio Code Insider version. However, the previous feature requires the users to select “Execute Using Profile<\/strong>” in order to see the coverage results, which is not intuitive. In addition, there is no coverage visualization in the editor area about your code on which is covered or not. In our latest pre-release version, we have made improvements for both of these issues. Now you can get to test coverage by just clicking the “Run Test With Coverage<\/strong>” button right next to “Debug Test” (Please note the icon is still a placeholder and will be changed). Here’s a demo.<\/p>\n

\"Image<\/a><\/p>\n

In addition, you can see if the code is already covered by the test in the editor area.<\/p>\n

\"Test<\/a><\/p>\n

To use the new Test Coverage feature, please make sure you have both Visual Studio Code Insiders<\/a> and Pre-release version<\/strong> of Extension Pack for Java<\/a> installed.<\/p>\n

Java Language Server Status UX Improvement<\/strong><\/h3>\n

Another UX improvement is about the Java Language Server status. Previously, users see the {} status icon<\/strong> only if current opened file is Java file. This is inconvenient for many users as Java projects might contain other types of files, especially for users who work on polyglot projects. In our latest version, we have made an improvement for the status icon. The icon is now parallel to {}<\/strong> for an easier access. In addition, now as long as Java extension is activated, the icon will display the status of the Java Language Server, regardless of the current opened file. The pictures below demonstrate the difference.<\/p>\n

Before\u00a0<\/strong><\/p>\n

\"Java<\/a><\/p>\n

After<\/strong><\/p>\n

\"Java<\/a><\/p>\n

Fix for “Editor Content Out of Sync” Issue<\/strong><\/h3>\n

Reliability has always been our top priority, and recently we discovered an issue<\/a> that causes editor content to be out of sync with the Java Language Server, which will in turn report false errors. This has been reported by users in our survey as well as on GitHub.<\/p>\n

We have already released a fix for this issue. After the release, we have observed in a notable reduction of occurrences. If you encounter any further problems, please do not hesitate to create an issue<\/a> here.<\/p>\n

Install Extension Pack for Java<\/strong><\/h3>\n

To use all features mentioned above, please download and install Extension Pack for Java<\/a> on Visual Studio Code.<\/p>\n

\"Extension<\/a><\/p>\n

If you are a Spring developer working on a Spring Boot application, you can also download the Spring Boot Extension Pack<\/a> for specialized Spring experience.<\/p>\n

\"Spring<\/a><\/p>\n

Feedback and suggestions<\/span><\/strong><\/span><\/h3>\n

As always, your feedback and suggestions are very important to us and will help shape our product in future. There are several ways to give us feedback<\/p>\n