A new WebStorm 2018.2 EAP is now available! What’s new: - Extract React component refactoring - Global File Watchers - Improved support for Angular CLI schematics - Rerun failed tests More in https://blog.jetbrains.com/webstorm/2018/06/webstorm-2018-2-eap-182-3341 …pic.twitter.com/NhH8YwiYpd
-
-
Replying to @WebStormIDE
Hmm class based component extending PureComponent by default?
1 reply 0 retweets 0 likes -
-
Replying to @Kelset @WebStormIDE
I personally would default to a functional component.
1 reply 0 retweets 3 likes -
We've been thinking a lot about the defaults and decided to go with PureComponent for class components and function (vs arrow function) for functional. But it's all customizable. We hope to get the feedback on that now, before the stable release and make changes if needed.
2 replies 0 retweets 1 like -
I think the option that makes most sense is functional component by default, with the “class” option being React.Component.
1 reply 0 retweets 9 likes -
Dan, Oleg, thanks for the feedback, it's really valuable for us now! We'll give it a second thought and try the new defaults in the next week's EAP build.
2 replies 0 retweets 7 likes -
Replying to @WebStormIDE @dan_abramov and
+1. PureComponents could be dangerous as long they will block all the changes, they are not aware of. Literally - all the changes, sometimes.
1 reply 0 retweets 0 likes
Thanks for the feedback. We'll switch to Component as a default in the next week's EAP build.
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.