Saloneer

_From @wied03 on March 28, 2016 15:56_ And I'm cool with doing a PR for this since I already wrote it in react-opal. I'm mainly curious about the cache question...

_From @ajjahn on March 29, 2016 2:56_ @wied03 That cache was added to address #124 and #125. @catmando You implemented a fix for the 0.7.x branch (in a different way)....

_From @wied03 on March 29, 2016 3:24_ @ajjahn - I'm not really as curious about why the cache is there as much as how you know when to clean it...

_From @catmando on March 29, 2016 15:31_ okay so if part of the confusion is being caused by _react_params_conversion, then lets wrap up that discussion. ( #96 )

_From @ajjahn on March 29, 2016 15:50_ @wied03 The cache for a prop busts if the underlying component's prop has changed. There isn't a need to mark the entire cache...

_From @wied03 on March 29, 2016 15:55_ I'm guessing that the complexity of the cache is worth it? Was it really that expensive to do the camel case/native conversions on...

_From @ajjahn on March 29, 2016 16:28_ @wied03 I don't believe camel case/native conversion was the primary reason. The problem here is react.rb has some reactive-record feature envy. Reactive record...

_From @ajjahn on December 9, 2015 22:53_ How about a `:scope` option? Also, I like the idea of the `:access` option mirroring Ruby's built in `attr_reader`, `attr_writer`, `attr_accessor` terminology. I...

_From @catmando on December 10, 2015 0:14_ 1) Not sure what scope: :shared even means? Can you elucidate? 2) Not sure about MyComponent.state.foo. I've thought about it, and I'm unconvinced....

_From @ajjahn on December 10, 2015 2:1_ I'm going to address your 4th question first. I do not think state declaration should be optional. In https://github.com/zetachang/react.rb/issues/89#issuecomment-162732528, I outline many issues...