Issue #28  (Using GitHub with VS Code)11/02/22

As I briefly mentioned in a previous issue, if you want to view all the settings you've modified in a single place, you can open your Settings UI and type "@modified" in the search box. This will filter your settings to only show you the settings with the blue strip next to them (i.e. all your modified settings).
 
And, as is always the case when searching your settings, VS Code categorizes your settings, providing navigation on the left side so you can easily find modified settings in a particular category.

Any settings you change in the Settings UI will also be reflected in JSON format in the JSON settings. You can see all your modified settings when using the JSON split view. The pane on the right is where you can edit your settings in JSON format if you choose. All your settings are included here more or less as a wall of text, so it's not too readable in terms of categories and whatnot.


 

As a suggestion, why not go through the JSON version of your settings, move the settings around, categorizing them in a way that's easier to deal with? You can see how I've done so in the screenshot below.



I'm sure many of you, especially those who mainly use the JSON version of the settings, already do this. But it's a good tip for those just getting started with customizations and probably a good idea to do this before your customizations get too unwieldy.

Any new settings changes that you make in the Settings UI will be automatically added to the bottom of your JSON file. So every once in a while, you can move the new changes to the correct category. Just make sure to use the correct JSON syntax (comma after each entry except the last), which can get a little messed up if you start copying/pasting to move things around.

Now on to this week's hand-picked links!
 

VS Code Tools

Nanowise Galaxy — A slightly punchy dark theme for VS Code that lets you "take a trip through the galaxy and experience the clean silence."

Dart Code — Dart and Flutter extension for VS Code that adds support for the Dart programming language and tools for effectively editing, refactoring, running, and reloading Flutter mobile apps and AngularDart web apps.

Auto Import — VS Code extension that automatically finds, parses, and provides code actions and code completion for all available imports. Works with Typescript and TSX.

Front Matter —  A CMS that runs within VS Code that gives you the power of a full-blown CMS while providing the flexibility and speed of the static site generator of your choice (Hugo, Jekyll, Hexo, Next.js, Gatsby, etc).
 

VS Code Articles

Setting up Visual Studio Code for Web Development – For Beginners and Intermediate Developers — Zell Liew goes over a simple setup for developing in VS Code, with plans to expand on this in a future article for advanced users.

Resolving Merge Conflicts with Visual Studio Code — Discusses the new 3 way merge editor feature, introduced earlier this year for VS Code.

Visual Studio Code: Remote Code Execution — This vulnerability is now patched, as explained in the issue, and you can read related info and discussion on this Hacker News thread.

Streamline Your Apple Device Management — Jamf Now makes it easy to deploy, oversee, and secure all your devices. Sign up for a free account now with capability to manage three devices and add more for just $2 per device each month.  Sponsor 

Best of the Rest

5 NeoVim GUI Editors You Could Try If You are Not a Total Terminal Junkie — Some GUI tools that might be useful for those more familiar with visual tools like VS Code instead of terminal-based ones like Vim and Neovim.

WebStorm 2022.3: New UI Preview, Vue and Angular Improvements, and Vitest Support — The latest updates from WebStorm by JetBrains, with some additions of interest to front-end developers.

ERA — A privacy-friendly markdown-based note-taking tool for developers, for notes and documentation, available for macOS, Windows, and Linux.

Suggestions?

If you have any link suggestions, including a tool, article, or other resources related to VS Code or another IDE, send it via DM on X: @LouisLazaris or just hit reply on this email.

That's it for this issue.

Happy VS Coding!
Louis
VSCode.Email
@LouisLazaris