Walkthrough is a multi-step, wizard-style experience for onboarding users to an extension featuring rich content. Ever since Visual Studio Code introduces the walkthrough format for extensions, it has become widely popular. Since we have made a lot of improvements for Spring extensions, we also made a refresh for the existing walkthrough for the Spring extension pack.<\/p>\n
The new walkthrough reflects our latest features such as beans and API mapping views as well as live memory graph from the Spring Boot dashboard. It also contains more concise and intuitive information so new users can learn about how to use the Spring extensions in a smooth way. Here’s a demo for the new walkthrough.<\/p>\n
The new walkthrough consists of four steps<\/p>\n Step 1 – Start with a Spring Boot Project.<\/strong><\/p>\n In this step, you can either use the Spring Initializer to create a project from scratch or clone an existing sample project from GitHub.<\/p>\n Step 2 – Explore your projects<\/strong><\/p>\n Once you have a project, there are different tools in the extensions that can help you quickly navigate to Spring symbols. Beans and endpoint mappings are part of the Spring Boot dashboard UI layout and you can directly jump to the view in this step.<\/p>\n Step 3 – Run your projects<\/strong><\/p>\n This step explains how to run the project. To enjoy the most Spring features from our extensions, you can click the Play button from the Spring Boot dashboard. Alternatively, you can use other methods described in this step.<\/p>\n Step 4 – View live information from your running application<\/strong><\/p>\n A unique feature of our tools is the ability to visualize the live data for a running Spring application. The see the live data, run the application from the Spring Boot dashboard. You will be able to see the beans, endpoint mappings as well as newly added live memory information.<\/p>\n When editing code, sometimes developers want case of the letters to be taken into consideration. We have heard this feedback from the developers and have added this feature in our extension. Here is a demo for this feature.<\/p>\n Please note that this feature is currently available in Insider version only, and will later be released on Stable version<\/strong>. To switch this feature on or off, please go to the settings and search for “match case”. Here’s the screenshot.<\/p>\n Long project index time is an issue we constantly hear from developers, and we’ve been looking for a good solution. Recently, we have made an improvement from the upstream to reduce the overall project index time. Previously, the index files for each workspace are stored separately, and require rebuilding all indexes during project imports, that could result in a long indexing time. However, after the improvement, we chose to store the indexes for libraries in a common location so that different workspaces can reuse the same index files. It saves the time for duplicate indexing of common libraries (such as JDK and popular libraries) and significantly improves indexing performance.<\/p>\n We have ran some experiments and here’s the performance benefits that we can get the share indexes.<\/p>\n![\"Spring](\"https:\/\/devblogs.microsoft.com\/java\/wp-content\/uploads\/sites\/51\/2023\/01\/springwalkthrough.gif\")
<\/a><\/p>\nCase sensitive code completion<\/strong><\/h4>\n
<\/a><\/p>\n<\/a><\/p>\nPerformance improvement – Reduce project index time by sharing index files\u00a0<\/strong><\/h4>\n