Timeline feature previewed! Visual Studio Code 1.42 update summary

Hello.
I'm Mandai, the Wild team member in charge of development.

This month, we received an update for VSCode (hereinafter referred to as Visual Studio Code), so I would like to introduce some of the features that I personally found most appealing

Unsaved editor behavior is now much better

I would like to see a feature implemented soon that stores data even when it is unsaved, but it seems that this is still a long way off (and there are no plans for such a feature)

There are two improvements this time

First, the editor title, which is currently "untitled," now displays the beginning of the content, making it easier to identify.
While it's debatable how often you'd actually open an "untitled" editor, this is the first improvement.

The other is an improvement to the behavior of the default language mode

For example, I have my default language mode set to Markdown.
This is so that I can take notes immediately whenever I feel like it.

That's fine if you just want to take notes, but if you want to copy the contents of a file, this setting becomes a hindrance

A new option has been added: you can set the string ${activeEditorLanguage} to create an editor with the language mode set to the same as the language mode of the editor that was previously open

The code is in TypeScript, but the configuration file is a json file, a yaml file, or maybe even .env, so it's common to choose the most appropriate file format depending on the content, and if you often have a mixture of various file formats, I think this setting is fine

This setting can be set for each workspace, so you can set ${activeEditorLanguage} for your development workspace, and if you're creating a workspace for taking notes like me, set it to Markdown, and you'll probably be even more efficient if you do that

 

Panels can now be moved to the left side of the editor

Previously, this panel could be moved to the right (as I recall), but now it can also be moved to the left

This panel also includes a terminal, which is very useful when viewing logs with less (although it would be nice to have it on the right side)

While you'd ideally want to use keyboard shortcuts to quickly move panels like this, the shortcuts themselves are set up but not assigned to any keys, so you need to configure them yourself.
Try searching for "workbench.action.positionPanelLeft" and assigning it to a key.

 

Rename preview feature added

One of the tasks that requires careful consideration during refactoring is changing class names.
Ideally, it's best to avoid changing them, but it's quite common for a class name to become inconsistent with its actual implementation after subdividing a class.

It would be great if the test could successfully pick up any oversights, but that doesn't always work, so it's a task that requires quite a bit of courage

In such cases, using Rename Preview will display a list of all occurrences of the class in the project, which will likely reduce the chances of missing something

However, this feature seems to depend on the implementation of IntelliSense, and is therefore dependent on the Language Server implementation.
From what I've briefly researched, JavaScript and TypeScript are supported by default, but for other languages, it seems to depend on whether IntelliSense supports them.

 

You can now set the maximum number of editors open

It depends on the Language Server you are using and the size of the content, but generally one editor uses more than 50MB of memory, so if you open 20 editors, it will consume about 1GB of memory

If you add a development environment to that, memory will run out in no time

Therefore, a feature has been added to allow you to set a limit on the number of editors that can be opened in VS Code.
This makes it possible to limit the amount of memory that VS Code uses.

• workbench.editor.limit.enabled
• workbench.editor.limit.perEditorGroup
• workbench.editor.limit.value

The above three setting items have been added, so let's check the role of each

First, let's look at `workbench.editor.limit.enabled`. This setting determines whether to enable or disable the editor's data limit.
By default, it's set to `off`, meaning it's disabled.

Next is `workbench.editor.limit.perEditorGroup`.
This setting determines whether the maximum number of editors is applied per editor group or to the entire editor group. When applied
per editor group, it seems less like a resource limit and more like a control to prevent editor tabs from becoming too small.

Finally, there's `workbench.editor.limit.value`, which is the maximum number of editors that can be opened.
The default value is 10.

 

New features are being unveiled one after another in the Insiders Edition

The Timeline feature, as specified in the current milestone, is now in preview

This is a feature that allows you to check the commit history on a file-by-file basis, making it easy to check the past modification history for each file, which was previously difficult to track using gitlens' commit history

It seems that the timeline API has already been added and can be used by extensions

The search function will also be completely revamped, and the new search function will appear as an editor rather than being displayed in a sidebar or panel

The biggest difference I noticed when using it is that the search results are displayed in the editor, allowing you to export the results as a file. I had
n't really considered the inability to save multiple search results before because it had always been like this, but now that you mention it, it would be better if you could save them.

Now that it's an editor, the freedom of expression has increased dramatically, and I found it very easy to read.
Also, there are links that allow you to quickly go to the location of the search results, so the user experience is almost the same as before.

The above features are not available on the official website, but Insiders are available to

 

summary

This update seemed to focus on adding many new features related to settings. What did you think?
Due to space limitations, we couldn't introduce all of these, but there are other thoughtful additions such as the ability to specify the default behavior when a conflict occurs during saving, and a function to highlight lines that have been folded in code. Please try them out!

positioned as a feature evaluation version, Visual Studio Code Insiders allows you to try out exciting new features such as the timeline and new search functions in advance, so I think it's worth installing.

I was truly confused for a moment. I was
so distracted by the twins that I didn't even look at the product, but it's 4600 yen...?

That's all