Timeline feature previewed! Visual Studio Code 1.42 update summary

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

An update to VSCode (hereinafter referred to as Visual Studio Code) has arrived this month as well, so I would like to introduce the features that personally caught my attention.

The unsaved editor behaves much better.

At the earliest, I would like to see a feature that stores files even when they are unsaved, but that seems like a long way off (there are no plans for such a feature).

There are two points that have been improved this time.

First, the beginning of the content is now displayed in the untitled editor title, making it easier to identify.
There is also the question of how many untitled editors are opened, but this is the first improvement point.

Another improvement is the behavior related to the default language mode.

For example, in my case, the default language mode is set to Markdown.
This is because I want to be able to take notes immediately when I want to take them.

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

As a new option, you can now set the string ${activeEditorLanguage} to create an editor that is set to the same language mode as the previously opened editor.

The code is in TypeScript, but the configuration file may be a json file, a yaml file, or even an .env file, and it has become commonplace to choose the most suitable file format depending on the content, so a variety of file formats are mixed. If you often do this, I think this setting is a good choice.

This setting can be set for each workspace, so set ${activeEditorLanguage} in your development workspace, and if you create a workspace for writing notes like me, set Markdown. I think it would be even more efficient if you left it there.

 

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

Previously, the panel could be moved to the right (or so I remember), but now it can also be moved to the left.

This panel also includes a terminal, so it's very convenient when viewing logs while using less (although it could be on the right).

I would like to use shortcut keys to move panels like this, but although the shortcuts themselves are set, they are not assigned to keys, so I have to set them myself.
Try searching for "workbench.action.positionPanelLeft" and assigning it.

 

Added rename preview function

When it comes to refactoring, one thing to be careful about is changing class names.
It's better not to change it if possible, but I think it's common for a class to be subdivided, resulting in a discrepancy between the class name and the actual status.

It would be great if I could catch up on things I missed during the test, but sometimes that doesn't happen, so it takes a lot of courage.

In such a case, if you use Rename Preview, it will display a list of all the occurrences of classes in the project, so I think you will be able to reduce the number of things you miss.

However, this feature seems to be based on the implementation of IntelliSense, and seems to depend on the implementation of Language Server.
I did a quick search and found that JavaScript and TypeScript are supported by default, but other languages ​​are only supported if IntelliSense is supported.

 

You can now set the maximum number to open in the editor

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

If you add the operating environment for development to that, you'll quickly run out of memory.

Therefore, we have added the ability to set a limit on the number of editors that can be opened in VSCode.
This allowed him to limit the memory used by VSCode to some extent.

• 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 one.

First, workbench.editor.limit.enabled is an item that determines whether to enable the editor limit setting.
By default it is off and disabled.

Next is workbench.editor.limit.perEditorGroup.
This item determines whether the setting for the maximum number of editors is applied to each editor group or to the entire editor group.
It seems like this is a control to prevent editor tabs from becoming too small, rather than a resource limit for each editor group.

The last one is workbench.editor.limit.value which is the maximum number of editors to open.
Default is 10.

 

New features are being unveiled one after another in the Insiders edition.

The timeline feature specified in the current milestone is now in preview.

This is a function that allows you to check the commit history of each file, and it is now possible to easily check the past modification history of each file, which was difficult to keep track of using the gitlens commit history.

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

It also appears that the search function will be completely redesigned, and the new search function will appear in the editor rather than in the sidebar or panel.

The biggest difference when using it is that the search results are displayed in the editor, so you can output the results as a file.
Not being able to save multiple search results has always been like this, so I no longer think it's an inconvenience, but if you ask me, being able to save it would be better.

Since I became an editor, the degree of freedom of expression has increased dramatically, and I thought it was very easy to read.
Additionally, there are links that take you quickly to the location of the search results, so the experience remains largely the same.

The above features are published on Insiders

 

summary

This time I got the impression that there were a lot of new features related to settings, what do you think?
There are also some clever additions, such as specifying the default behavior in the event of a conflict when saving, and highlighting code-folded lines, which I couldn't introduce due to space limitations, so please try them out.

I think it will be fun to install Visual Studio Code Insiders which is positioned as a functional evaluation version

I was really confused for a moment.I
was too distracted by the twins to look at the product, but it's 4,600 yen...

That's it.