Mitch VanDuyn
Mitch VanDuyn
Can this mechanism be used for all these cases (browser, active support, rails helpers) Will this still work if the user wants a different version of react.js?
@ajjahn - I think the concern is not with the size of the component. In fact this came up when reading a very small component... The problem is to distinguish...
From a discussion from the chat area it would seem the best approach is to divide this into separate gems: reactrb-prererendering-support that takes provides anything a prererendering pipeline needs (i.e....
again the suggestion of either a basic vs. full version would answer this, or somehow making it configurable.
@derikson - good point. The difficulty I think is more "syntactic" as in how to get this to all work nicely within the DSL, such that its easy to create...
Sure in react when you update a state, you cannot immediately read the state and be guaranteed to get the value back till after the render. This makes sense in...
FYI... I am working on changing the way the dsl references Opal components: right now if the component is `class FooBar` then the dsl references it as `foo_bar` The ReactJS...
That's exactly where I am heafing
I tried out using a const name (i.e. FooBar instead of foo_bar) for client defined components. It works nice, unless the component has no block and no parameters (I think...
Okay! Got component classes to name space correctly, and things read quite nicely... in addition I setup a full two linkage (based on React Linkages) that allows a single param...