You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2018. It is now read-only.
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.
if you say for example:
MyRubyComponent().on(:change)
then MyRubyComponent will receive aonChange
param. But if you sayMyRubyComponent().on(:foo_bar)
then MyRubyComponent will receive aon_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.
The text was updated successfully, but these errors were encountered: