Mitch VanDuyn
Mitch VanDuyn
All callback handlers that take parameters (component_will_receive_props, component_will_update, component_did_update) as well as should_component_update? are actually broken ATM. The params to these methods are hashes, and the `create_native_react_class` method was refactored...
Some react libs allow a component class to be passed as a "control". There is no easy to convert a Hyperloop::Component to the underlying JS component. It can be done...
Instead of requiring ruby racer we should: Check if it is present, if so use it for prerendering (if prerendering config is on) if not present and prerendering config option...
maybe we do this already???? I don't think so... Related to #122
Why can't we just convert all values returned by the tag's block to a string? If I say `li { foo }` and foo is for example a `Time` it...
`RenderingContext.render` builds a buffer of rendered elements. For example: ```ruby DIV do SPAN { 'span 1'}; SPAN { 'span 2' }; SPAN { 'span 3' } end ``` rendering the...
Implement the following pattern ``` ruby class Foo < React::Component::Base def self.my_components @my_components ||= [] end before_mount { self.class.my_components
children.empty? Seems to be just the way ruby works? perhaps there is a better way to define an enumerable?
Observables should be deprecated. This was largely a ruby-ized version of the old react.js links. There are better patterns now (i.e. events or stores) (@zetachang - there is a deprecation...
This is probably my fault, but this spec worked in 8.x, but in 9.x broke: ```ruby require 'spec_helper' describe Timecop do before(:each) do Timecop.return end it 'new connections expire' do...