You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's easy enough to make new optional but is there a good reason to do so? By adding the instanceof check at the start of every component, you've added extra bytes to everyone's application for the sake of allowing developers to write code that's actually less idiomatic. (With ES2015 classes, you have to use new, so over time new-less instantiation is going to seem ever more weird and out of place). Not to mention that it's a redundant check for nested components.
If it's purely to prevent errors, then maybe a development warning would be a better approach.
@brodybits do you have specific API suggestions? 'Make it like these other projects' isn't something we can work with, unless it's clear what you mean and why it would be an improvement 😀
new
keyword.In general I really like the idea of this project and would like to thank @nolanlawson for tweeting it.
The text was updated successfully, but these errors were encountered: