This might be the feature we were most looking forward to! Visual Studio Code 1.31 release summary!

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

Visual Studio Code (VSCode) version 1.31 has been released. The main topic of this
update seems to be that it's now more user-friendly, as it eliminates a minor but annoying issue.

 

You can now turn extensions on and off without reloading!

This is it!
The restart (which was basically a reload) that always occurred when installing extensions has now stopped.

If you've been using VS Code for a long time, you'll likely find yourself accumulating extensions that can become a
nuisance. Many of them load even though you're not using them in the currently open window. Disabling them on a workspace-by-workspace basis can improve things somewhat, but the reluctance to reload can make it difficult to do so.

The main reason I don't want to reload is that it erases the file history, which meansCtrl + ZI can't use
I'm the type of person who can't reload unless I first save all the information that's currently in memory to a file.

For example, when developing an API, you don't need the Chrome debugger

By the way, this feature seems to have been one of the most requested features for VSCode, so I'm really glad that it has been released

 

New Tree Widget!

It appears that the tree view widget module has been replaced with a new one

While performance improvements are certainly a plus, the ability to filter files by filename is a subtly welcome addition.
The user interface is slightly different from before, so I think it might need some further adjustments, but it's extremely convenient when you want to search by filename.

This is reassuring for those times when code completion doesn't work and you have to search for files.
Additionally, there are three modes available for displaying search results: simple, highLight, and filter.

`simple` matches the entered string from the beginning and switches focus to files that match.
`highlight` displays the input result in the upper right corner and highlights files whose filenames contain that string.
`filter` displays the input result in the upper right corner, similar to `highlight`, but displays only files that partially match.

I tried all the modes, and I found the filter to be very responsive and easy to use.
intuitively ESC deselect filtering with the
The setting key is "workbench.list.keyboardNavigation," so please try using the setting that suits your preferences.

This new tree widget seems to have several other features as well.Ctrl + a, adjust the directory indentation size in pixels using the "workbench.tree.indent" key, and choose whether or not to support horizontal scrolling using the "workbench.tree.horizontalScrolling" key.

 

There was no cut command in the context menu

As the title suggests, the context menu (the one that appears when you right-click) previously lacked a cut command, but it has finally been added in this update.
As a VS Code user, I've always assumed that using shortcuts extensively is essential, so to be honest, I hadn't even noticed it was missing.

 

If you open the editor a lot, we've added a setting that you should check at least once

When programming, you often find yourself opening many editors as you trace back through inheritance, butCtrl + W, it feels like you're stacking the files in the order they were opened and closing them from top to bottom, almost like manipulating the address space of assembly code.

Even if you intuitively understand the concept of stacking, the items aren't always stacked in the order you want them to be deleted.
A new setting called "workbench.editor.focusRecentEditorAfterClose" has been added to control this behavior.

If you turn this setting off, when you close an editor, the focus will move to the editor on the right, so you can move the editors you still want to use to the left and close them all at once from the right

I personally think this feature is pretty cool

 

Have you heard of the Smart Selections feature?

Alt + Shift + →I just learned about the smart selection feature using
Unfortunately, VS Code's ability to analyze Japanese sentences is terrible, so using Smart Selections with Japanese text is not practical.

I'm hoping to find a good extension to solve this problem, but I can't seem to find one that's a perfect fit.
If anyone knows of one,Twitter I would be grateful if you could share the information on

 

Terminal now responds better to file paths

on a relative path within the terminalCtrlYou can now launch the editor by holding down

However, you cannot directly click on the results of the ls or dir commands; it seems that you can only do this if you have echoed the file name once

I think it would be extremely convenient if you could launch an editor directly from the results of the ls command, but I imagine that since the results of the ls command do not have ./ or anything attached, it might be difficult to tell whether they are file names or not

 

summary

This time too, version 1.31 was packed with new features

Personally, I've always wanted a filename search function in the tree widget, so I'm definitely looking forward to using it.
Now that the barrier to installing extensions has significantly lowered, why not try searching for your favorite extensions?

in the past"A compilation of extensions that make using Visual Studio Code more enjoyable | Beyond Inc.I've also written an article

 
That's all