When your file is detected as plain text and doesn’t feature proper highlighting, WebStorm now suggests resetting the potentially unwanted file type association right from the editor, without going to Preferences / Settings and configuring the file types manually.Įnhanced configuration for highlighting problematic code We have more Angular 14-related improvements in the works – stay tuned! New notification panel for tuning file type associations Give it a try and share your feedback with us. Angular classes marked as standalone do not need to be declared in an NgModule. Components, directives, and pipes can now be marked as standalone: true. Standalone components offer a simplified way to build Angular applications. The most important addition we’ve made in this release is support for Angular standalone components. We’ve been actively working on supporting Angular 14 in WebStorm. Support for Angular standalone components If you want to report a bug or submit a feature request, you can do so directly in our issue tracker. Try them out and share your feedback with us in the comments below. Important! WebStorm EAP builds are not fully tested and might be unstable.īelow you can find the biggest improvements in WebStorm 2022.2 EAP #6. You can also manually download the EAP builds from our website. The Toolbox App is the easiest way to get the EAP builds and keep both your stable and EAP versions up-to-date. WebStorm 2022.2 EAP build #6 is now available! To catch up on all the new features, check out our previous EAP blog posts.
0 kommentar(er)
