Mitch VanDuyn
Mitch VanDuyn
currently you have to define Hash._react_param_conversion(json, validate_only=nil) for the conversion to work. This should be built-in ``` ruby class Hash def self._react_param_conversion(json, validate_only = nil) if validate_only true else Hash.new(json)...
Currently some someplace is calling _react_param_conversion with only the first parameter (i.e. the second is being allowed to default) But OPAL does not check for missing parameters. So if you...
these should be added as methods on the Element class
for example `React.render_to_static_markup` should be `element.render_to_static_markup`, etc...
We need a rails generator 1) where does it go? can it go in the react.rb gem? that would be great, otherwise I guess we have to make a reactive-rails...
now that implicit state construction has been (tentatively) added, should we deprecate define_state? I believe so, why? Because it makes the connection between "state variables" and "instance variables" clear. You...
adds basic exception handler that handles exceptions during rendering and prints a meaningful error message. This has been an invaluable resource during our use of react.rb. Without this its much...
All my upcoming pull requests will be based on this one. This is just the minimal changes to get things working with Rails 3.2, plus I added a todo list...
Say you do this: `React.render(React.create_element(MyFatComponent), Element['div.navigation'])` and you forget to `require 'my_fat_component'` Nothing happens, and there are no errors or warnings. Instead the create_element binding (and similar) should make sure...
This is WIP, just to see what you think of the changes. For now its using my own copy of opal that better source mapping than the current version 0.7......