IT House April 26 news, according to Microsoft blog release, the recent Visual Studio Code Java April update released. This time, the Microsoft team has brought you many exciting updates to the underlying development experience, including Java 18 support, embedded hints for parameter names, new Java language server state interactions, better lambda expression support, and more.
Before the update, the Microsoft team wanted to share an exciting news: Microsoft JDConf is coming! Active registration is welcome to participate in the second JDConf event from 4 to 5 May 2022. This is a Virtual Java-themed conference where developers can get together to share topics about Java. The goal of the Microsoft team's event is to highlight and showcase the outstanding work being done by the entire Java community.
https ://aka.ms/jdconf
Java 18 support
The Microsoft team has been committed to supporting the latest Java technologies. With the full release of the GA version of Java 18 in March of this year, Microsoft Teams has also enabled support for Java 18 in the latest version. This means you can now use Java 18 in your projects!
Support for embedded hints for parameter names (Inlay Hint)
When writing code, do you sometimes wonder which parameter you're filling in? In some functions that use literal values as arguments, do you want to know what value you provide? Here's the good news! Embedded hints will solve these problems for you! In the latest version of Microsoft Teams, Microsoft Teams enables this feature for Java projects. When enabled, Visual Studio Code displays hints for parameter names in the method signature, a feature that has three modes.
None (disables parameter name prompting)
literal (enables parameter name hints only for literal parameters) (default)
all (enable parameter name hints for all parameters)
You can change this setting at any time by going to the "inlay" setting under Java
New Java language server state interaction
Previously, there were multiple items on the status bar to display the current state of the Java language server, which sometimes made the interface crowded and cluttered. Since version 1.65, Visual Studio Code has completed its new Language Status Item API. In the latest version of Microsoft Teams, Microsoft Teams not only adopted the new API, but also made some minor tweaks. If you update to the latest version of the Visual Studio Code and Java plugin package, you'll see that the various language server states have been consolidated into a unified item, which is not only more concise, but also provides developers with more operations and more from a single place.
Currently the portal provides the following information and actions:
If a problem or error occurs, you'll see an indicator on the status icon, and you can click Show Problem to display the error details.
The Microsoft team hopes that this improvement will provide a better user experience for the state of the Java language server, please share your feedback with the Microsoft team so that the Microsoft team can continue to improve the area.
Completed its new language status item API
https://code.visualstudio.com/updates/v1_65#_language-status-items?ocid=AID3042760
Java plug-in package
https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack
A code operation that extracts the lambda body to a function
As a minor feature update, the Microsoft team also added a code action (from Quick Fix) to allow developers to easily extract lambda bodies into functions. Here's a quick demo:
Support for Lambda expressions in debugging
Finally, the Microsoft team wanted to provide some updates to support for lambda expressions in debugging. Previously, a user on an issue on GitHub found that the plugin did not properly evaluate variables in lambda expressions during debugging. In the latest version of Microsoft Teams, Microsoft Teams has fixed this issue. The following is a quick demonstration of evaluating variables when using lambda in chained calls:
For a complete list of all support cases, visit the original Issue.
Issue
https://github.com/microsoft/vscode-java-debug/issues/754