We haven’t been able to invest resources into Svelte much lately, so unfortunately, the quality of the support has deteriorated. Svelte support has been available as a separate plugin for a few years now. Also, symbols like enums used outside of a template or component will be automatically imported on code completion or when using a quick-fix ( WEB-58268). For v15, we’ll add an inspection that suggests using ngSrc instead of src for img ( WEB-58267). In addition to WEB-32784, we want to implement two new features for Angular. Additionally, we’ll make WebStorm automatically import components and other symbols when copying and pasting template code between components ( WEB-32784). We plan to provide completion for custom component events ( WEB-52121) and support the type cast syntax in the template expressions ( WEB-55049). There are a few more issues we’d like to fix in the next release to improve the Vue support. We fixed over 40 Vue-related issues in WebStorm 2022.3. Please see WEB-50449 for more information. For now, the support will be available via a separate plugin, but we’ll consider bundling it next year. Although we didn’t announce our plans regarding Prisma ORM support in the previous roadmap, we did work on adding it between the 2022.1 releases. We’ll support more advanced features if there’s time for that. For starters, we want to make sure that at least the basic functionality like syntax highlighting and code completion works well. We’re going to add support for the Astro framework ( WEB-52015). In the meantime, we want to share our plans for the next release, which is scheduled for the end of March 2023. We’re still processing your feedback to understand what worked well and what could be improved. We’d like to thank all of you who have already tried it and shared your thoughts with us! We’ve had an overwhelming amount of feedback, with the new UI being the absolute leader in the number of mentions. The Close All but Pinned action now works as expected ( IDEA-256044).įor the full list of issues addressed in WebStorm 2020.3.3, please see the release notes.Last month, we rolled out WebStorm 2022.3, our final major update of 2022. Solved the problem with high CPU usage ( WEB-48983).įixed the bug with Git diff changes shown incorrectly ( IDEA-257651). Other notable improvementsįixed a number of regression bugs ( WEB-48038, WEB-49135, WEB-49137, and WEB-49156). If you store all your trusted work-related projects in a specific location on your machine, you can mark that location as trusted by adding it to Trusted Locations in Preferences/Settings | Build, Execution, Deployment. To warn you about situations where potentially malicious code might be automatically run by the IDE, WebStorm will ask you to confirm whether you trust the source. You might know that the IDE runs webpack configurations to properly resolve imports in your project. To learn more about it, check out this blog post. To mitigate the risks associated with opening projects from unknown sources, we’re introducing the concept of trusted projects. You can also download WebStorm 2020.3.3 from our website. You can update to this version right from your IDE or using the Toolbox App. WebStorm 2020.3.3, the third bug-fix update for WebStorm 2020.3, is now available!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |