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
Currently it always generates React classes but really, it could be a generic component builder that automatically decided the most appropriate React representation.
big win is that many components could be lighter functional components wrapped in React.memo. In my usage, most components are stateless and the only lifecycle method specified is shouldComponentUpdate
display name should be optional - not needed for functional components, could be automatically derived anyway (Automatic component name #470 )
output type would need to reflect decision meaning it needs to be a type-level calculation meaning we need to track more stuff at the type level meaning install methods that expect to be used by .configure now explode with types meaning yuk
would need a method to override automatic selection - users must always have full control
The text was updated successfully, but these errors were encountered:
most components are stateless and the only lifecycle method specified is shouldComponentUpdate
I have a question: this issue seems that the builder will choose between functional and class component only. Will it possible to generate a class component that extends from PureComponent?
Currently it always generates React classes but really, it could be a generic component builder that automatically decided the most appropriate React representation.
React.memo
. In my usage, most components are stateless and the only lifecycle method specified isshouldComponentUpdate
install
methods that expect to be used by.configure
now explode with types meaning yukThe text was updated successfully, but these errors were encountered: