This repository was archived by the owner on Oct 19, 2018. It is now read-only.
This repository was archived by the owner on Oct 19, 2018. It is now read-only.
event onChange does not map to on_change when attaching to ruby component #259
Description
if you say for example: MyRubyComponent().on(:change) then MyRubyComponent will receive a onChange param. But if you say MyRubyComponent().on(:foo_bar) then MyRubyComponent will receive a on_foo_bar param.
See
hyper-react/lib/react/element.rb
Line 122 in dc90b84
For why.
The reason this is done is that MyRubyComponent can pass all_other_params on to components nested within it, and the event names will follow along.
Perhaps rethinking the entire param interface between ruby and native components could yield a more consistent solution.