![]() Is it trying to automatically detect my npm scripts? For reference, Mocha’s scripts in its package.Some time ago I've started to write typescript on server-side. that needs some further explanation, but sure. What's do you call a widget like this, anyway? “Tasks” are not the same as “Tasks” in a WebStorm, which is WebStorm’s (leaky) abstraction around issues, staged changes and branching. I think a “Task” is perhaps a “Run Configuration” or “External Tool”. VSCode automatically enables Git support for working copies instead of prompting you into oblivion.VSCode uses the stage, unlike WebStorm.You will likely want to install the Git extension pack, due to VSCode’s basic client implementation.Next, I’ll run Mocha’s test suites to prepare for publishing. Not the nicest initial experience, but I’m confident it’ll be smoother sailing from here. I go ahead and commit everything (including unstaged changes this would be Git: Commit All if I wanted to avoid the prompt), and push. VSCode uses the stage, like literally every other Git client except WebStorm’s. If you only use WebStorm’s built-in version control client (I don't), this will be culture shock. But I’m prompted that the stage is empty. I find Git: Commit via the Command Palette, and realize I could have used my trusty ⌘-K. VSCode helpfully marks the file with a big M in the file list. I’ve made my changes to CHANGELOG.md, and it’s time to commit. The presentation of the repo is a little disorienting (there are so many trees, it's like a forest), but I do see the pulled changesets. ![]() GitLens then provides Git history in the left sidebar. Hint: run GitLens: Toggle Code Lens and GitLens: Toggle Line Blame Annotations from the Command Palette. GitLens does some oddball things like “inline blame” and “code lens” (which is another view into “blame”? I don’t get it). To VSCode’s credit, it aids discovery with tags, filters and sorting. This is a drawback of the “small core” philosophy of VSCode (this reminds me of the Node.js ecosystem). But there are many Git-related extensions for VSCode. GitLens seems to solve this problem (and others). After searching in vain, I realize that there is no built-in support for Git history, and I’m going to need to grab an extension for this. Which changesets did Git pull? I want to look at the history. I think it worked? It said "sync." What's a "sync"? To pull, I found a little “refresh” button in my status bar, and clicked it. Happily, VSCode understands this is, in fact, a working copy. But I know origin has changes I need to pull. OK, so I want to edit Mocha’s CHANGELOG.md. It’s difficult to discover what a particular keystroke does at any given time, but also supports conditionals, for a nearly absurd level of control.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |