- From: Majid Valipour via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Aug 2018 18:18:45 +0000
- To: public-houdini-archive@w3.org
_From @appsforartists on September 27, 2016 22:31_ Incidentally, one of the things React does really well is offer its component API in two flavors: - pure functions, for components that simply transform inputs into outputs, and - classes for components that track state over time. The natural thing for React users to do is author all components as simple functions until a case arises that needs local state, when they can upgrade that component to the more complex class API. I understand the desire for consistency across Houdini APIs, but also thought it was worth documenting my inspiration for opening this issue. -- GitHub Notification of comment by majido Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/809#issuecomment-417053620 using your GitHub account
Received on Wednesday, 29 August 2018 18:18:46 UTC