WebStorm’s superior refactoring tools are a big reason why I use it instead of @code, despite VS code having some nice features WebStorm does not.https://twitter.com/webstormide/status/981926057078083584 …
Thanks for the list! Do you remember what was the exact problem with Jest coverage? No additional configuration in WebStorm to build coverage reports is required - if coverage is enabled in Jest config, it should just work if you hit Run with Coverage instead of Run in WebStorm.
-
-
I’m talking about seeing the coverage in the gutter where the line numbers are. The entire process of having to run it through the run process is a pain. In Code, you literally enable it with one click.
-
WebStorm also shows coverage on the gutter. We will check how it actually works in Code and how we can improve the process in WebStorm.pic.twitter.com/83PcDHLnrR
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.