Visual Studio Code 1.29 release summary with improved search functionality

Hello.
I'm Mandai, in charge of Wild on the development team.
The monthly version update of Visual Studio Code (hereinafter referred to as VSCode) has arrived.
It seems that my articles are not regular every month...

I thought there were a lot of topics this month, so I counted them and found that there were 61 major topics listed in the release notes alone!

This time we have a lot to offer, so although not all of them, we have carefully selected the features that you will want to use!

Enhancements around search

You can now search using regular expressions that span line breaks, which was not possible before!

It is a strange feature that it has not been supported until now, but it is the most important feature listed in the first topic.

Other features include the ability to back reference within regular expressions and read ahead.
As server-side developers, we don't use these features often, but they are powerful when you want to inspect the inside of an HTML file.
On the other hand, I think this is a fairly impactful update for people developing front-ends.

If you are interested, a setting called search.usePCRE2 has been added to enable the PCRE2 engine, so let's enable it!

In addition, search.showLineNumbers adds line numbers to search results, search.useReplacePreview controls whether to open a preview when converting search results in bulk, and files such as .gitignore and .ignore that are globally available for search results Added functionality such as search.useGlobalIgnoreFiles to exclude files based on their contents.

 

Are you using it? breadcrumb trail

The breadcrumb trail has been enhanced, probably due to the strong push by VSCode's developers.
This time, you can now choose the order of the breadcrumbs from three options: order of appearance in the file, order of name, and order of symbol type.
This is the same as the outline sort order.

Additionally, when you select a file from the breadcrumb list and open it, you can click it with the middle mouse button to open it in a new tab that is not eligible for reuse.
This setting competes with workbench.editor.enablePreviewFromQuickOpen which does not reuse tabs.

By the way, the shortcut key to open the breadcrumb list is " Ctrl + Shift + : ", so feel free to use them together.

If you use breadcrumbs frequently, you can hide Explorer, which has the advantage of freeing up more horizontal work space.
Also, if you open the sidebar with " Ctrl + B " and move the focus to Explorer, you will not be able to return the focus to the editor, so if you use shortcut keys frequently, you will have to touch the mouse to return the focus. This is a negative point that cannot be overlooked.

 

Insiders preview of Electron 3.0 version released

In Electron3.0, the bundled Chromium has been updated to version 66.
Additionally, Node.js was also updated to 10.

By the way, even in the stable version, minor version updates of Electron are included from time to time, and with this update, the version has been upgraded from 2.0.9 to 2.0.12.

 

Writing CSS has become much more convenient.

A feature called CSS Specificity has been added to make it easier to see if CSS is being applied correctly.
I've done this kind of verification in my head a lot, so it feels like it's too late, but while CSS I wrote myself is easy to understand because I know the tricks, CSS written by others requires some getting used to reading. .

In such cases, CSS Specificity may be useful.

Also, something I still occasionally do is specify a value of 0px or 0%.
In the case of 0, you can just write 0, or rather, you should write it that way, but it seems that this is now clearly recognized as a warning.
When searching for a value while making adjustments, if the result is 0, you end up leaving the unit alone.

 

More shortcut keys have been added to make using the workbench more convenient.

One of the most recent updates to the workbench is that the editor can now be split vertically, horizontally, and vertically, allowing us to move into an era of split editors! Visual Studio Code 1.25 Release Summary | Beyond Inc. has set an incredible number of shortcut keys that work around the workbench.
Moreover, most of them have no key assignments, which is a win-win situation for everyone.

Another new shortcut key has been added to the workbench, which is rich in unassigned shortcuts.
And there is no stable key assignment!

To be honest, around the workbench, I only use the quick open view set to Ctrl + Q

Even if you assign the keys yourself, don't you still feel worried about what will happen if the key assignments overlap with super convenient functions that may be added in the future?

 

summary

Were there always this many? 1.29 was packed with a number of updates that made me question this, but what did you think of it?
Personally, there were so many features that I didn't really understand, so it took me a lot of time to research them, but I'm confident that I don't know much about creating extensions for VSCode, so about 1/3 of them were updates that didn't directly affect me. .

There are many updates related to debugging, but there are many features that you can only benefit from if you are not developing with JavaScript/TypeScript, and it seems like it will be a little while before other languages ​​are covered.
Currently, most of my writing is in PHP, so I feel a bit left out.

I recently read an article that says Github has the most projects developed using JavaScript worldwide, and the popularity of JavaScript can be seen from the support for VSCode.

Looking at the new additions has made me want to write Node.js again.

For me, it's enough of an update to have a simple but evolving terminal that I use often!

That's it.