Mitch VanDuyn
Mitch VanDuyn
context.foo vs. context[:foo] is just syntax sugar right? it can do the same thing under the hood. Interesting that React requires a proptype. So do we want to be consistent...
I realized I don't have the initializer in the above, but again would like to make it all consistent with param for ease of learning.
I'm leaving that to @ajjahn. I'm just going from the standpoint that there is no reason why we can't make context.foo work the same as context[:foo]. In fact it should...
right... so we want to redo the PropsWrapper (and validation too) so that it works for props, and context, plus it work for class level props, and special param types...
okay so if part of the confusion is being caused by _react_params_conversion, then lets wrap up that discussion. ( #96 )
That all looks good. In particular I really like this: ``` ruby mount(MyComponent).with_params(say: 'Hi') # Like capybara's visit '/some/url' # now we have a mounted component object in the current...
Okay, I did an initial implementation for testing our site, and here is what I have come up with (just the mount so far) 1. because I want to support...
yes no problem
@fkchang had this comment which triggered this issue: I suspect this might be related to that issue u reported on the opal gitter -- but I'm wondering the right way...
Maybe if type is Native as in `param :foo, type: Native` it means to convert incoming to a string, then JSON parse it, and if that fails just wrap it...