I’ve already mentioned several extensions and explained how I use them. You need a GitHub token to configure it, but afterward, you just need to run a single command to upload and download your settings. However, Settings Sync helps you save your code settings as a Gist and allows you to sync your workflow between multiple machines. The native solution is only available to insiders at the moment. There’s not much point in customizing anything if you can’t back it up and reuse it whenever you need it again. The extension then runs a script that creates a folder and initializes this new component. Using New Component, I can specify the name and location of the new component. The video below shows Supercharge React in use. But creating a new folder and initializing files in it can be tedious. is something I do frequently, and it’s quite straightforward, as most readers will know. Code GenerationĬreating a new component, page, etc. I find a secondary advantage to doing aliases-spending less time typing them helps me stay focused and not lose my train of thought because I’m not trying to remember how to invoke the command. Saving a few characters here and there might seem silly, but these time-saving features add up in the long run. gdab = git branch | grep -v "master" | xargs git branch -D - deletes all local branches except master.del=RMDIR /S/Q $* & echo "Deleted Successfully!!!" - deletes the provided directory and shows a success message when it’s done. ys = yarn start - helps me start an app with just two characters.I’ve integrated them with VSCode and added many aliases (shortcuts) that save me time from writing commands. If you’re a Unix user, look up iTerm (macOS) or Oh My Zsh (Linux and macOS). Regardless of the OS you use, you can do better than the default terminal. The video below shows that all you need to do is right-click on the test name and use the context menu to run it. This useful extension allows you to execute or debug individual suites or tests. However, the native regex solution is quite clunky. I write one test at a time, which means I need a way to run one test at a time. People work in different environments and projects (for me, it’s mostly working with React.js and TypeScript on Windows), but the overall approach is valid for everyone. What I do won’t necessarily work for you, at least not entirely. In this article, I intend to explain how I addressed each one of these points myself and equip you with the knowledge to do it on your own. Continuously improve your workflow and keep track of your IDE’s evolution.Automate all the boring and repetitive tasks.Customization: Power users tailor their workflow to fit their specific needs.Intimate knowledge of your IDE: VSCode has excellent documentation, read it!.Here is what distinguishes a regular user from a power user:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |