You can inspect the history of files and directories and do rollbacks. WebStorm automatically tracks all the changes you made to your files and protects you from accidentally losing these changes.
#Install webstorm over and over code#
VS Code does not save a local history of your changes, but you can use extensions like Local History. You can commit files, review changes, and resolve conflicts with a visual diff/merge tool in the IDE. WebStorm provides all the functionality for complex git workflow out of the box. You can either use extensions like GitLens or use additional tools like Sourcetree if you like to use a GUI for complex git work. VS Code has, per default, a pretty basic git integration. VS Code has currently no possibility to show this information: WebStorm shows if there are unresolved promises (in this case for a TypeScript application): Not waiting for promises can be tricky if you expect the following code to run only after the promise has been resolved. There is currently also a VS Code Karma Test Adapter in development which should provide a similar integrated Karma test functionality for VS Code. Alternatively, I use the karma-jasmine-html-reporter, where you can also define to run only specific tests by clicking on them on the HTML page. fdescribe) which tells Karma only to run this specific test block. My Angular unit test workflow in VS Code is typically to mark a describe or it test block with a f (e.g. The following image shows such a test run: Running my jasmine & Karma tests in WebStorm I can easily jump to the failed test code and rerun only this specific test. You can run your tests directly from the IDE and even debug them there. WebStorm has an integrated test runner, which I like.
This feature convinced me that using WebStorm results in a cleaner code base. To see the difference open your project, which was developed in VS Code with WebStorm, and run the code inspection. This can significantly impact the code quality of a sizeable Angular code base, which was mainly developed using VS Code. But if you are, for example, using a TypeScript project (like Angular) VS Code does not detect unused public methods. You can also detect unused methods in JavaScript methods using VS Code and ESLint with the rules no-unused-vars and no-unreachable. It also indexes your whole project and can, for example, detect all unused methods, variables, and more.
This analysis detects any language and runtime errors and suggests corrections and improvements. WebStorm provides a robust, fast, and flexible static code analysis.
In the following article, I talk about my experience using WebStorm in a sizeable Angular application that was mainly developed in VS Code. This is a scorching topic, and I know this will cause some controversy. If I talk about using WebStorm, I also talk about using IntelliJ IDEA.
#Install webstorm over and over plus#
IntelliJ IDEA provides the same functionality as WebStorm plus a lot of other features.
0 kommentar(er)
