Mitch VanDuyn
Mitch VanDuyn
currently `.while_loading` is attached to a component like this: ```ruby Component(p1: exp1) do ... render some stuff end .while_loading do ... render this stuff if loading end ``` Now that...
otherwise in future you will have REACT::VERSION = 1.2 then you upgrade to 1.3 for some minor thing and now all other gems have to be re-released even though nothing...
currently you cannot say this: ```ruby Foo do lambda (x) { DIV { x } } end ``` even though its legal JS... i.e. we only allow strings or other...
Components can be provided a key, via the special `key` parameter that ensures when rendering lists of components the ordering does not change, and speeds up the rendering of the...
currently all (many?) of the specs are using the soon to be deprecated old style lower case HTML tags. I.e. `div` should be `DIV`. etc. etc. etc.
Not sure if this was a regression that got fixed or what, but we need to add a test case like this: ``` it "will preserve boolean values correctly" do...
Hyper-react (hyper-store actually) bundles all state changes and fires them *after* the end of the render cycle. This defaults heuristics in React's handling of inputs. Only way to see this...
there are three "modifiers" when a component is mounted: `on(...)` `while_loading` `after_error` (proposed, but will probably be added in 1.0) A proposal is to make these consistent like this: `on(...)`...
Group all state updates in a given render cycle together ```ruby module React class State def self.set_state(object, name, value, delay=true) states[object][name] = value if delay || @bulk_update_flag @delayed_updates ||= Hash.new...
_From @zetachang on February 18, 2015 16:41_ ## React - [x] React.createClass - **not valid**, `React.create_element` automatically cache the component class - [x] React.createElement - [ ] React.createFactory - [x]...