Mitch VanDuyn

components should accept any number of params to be merged

3

for example ``` ruby div(attributes, {more: :stuff}, :big, id: "hello", style: {display: :none}) ``` should be the same as ``` ruby div(attributes.merge {more: :stuff, big: true, id: "hello, style: {display:...

should_update? passing in native objects and expecting native true false return

1

should_update? passes two native object hashes (for new params, and new state) and only works properly if true or false are returned (i.e. nil does not work as false) This...

dom_node does not work on native components

1

i.e. if you use ref to get the id of say a "div" then you can't say ref["my_div"].dom_node as you would expect. ``` ruby class Foo < React::Component::Base after_mount do...

use event handlers instead of procs for callbacks

3

Instead of passing procs to components for callbacks, use the event mechanism / syntax. Thus `MyComponent(zee_callback: -> (x) { puts x }...)` becomes `MyComponent(...).on(:zee_callback) { .... }` It just looks...

inconsistent automatic snake case to camel case conversion

2

We need to clean this up for example the html attribute `default-value` should be expressible as `:default_value` or `"default-value"`. Sometimes things are getting converted, sometimes not. Also conversions should only...

component testing

5

Need some way to test components. Right now no reason why capybara will not work, but that is for testing entire view (or component tree), but we should have a...

Stateless Components

3

React now has this notion of a "stateless" component, by which they mean a JS function that takes the "props" as it param, and generates an element. Its stateless because...

class: does not work well as a parameter for application classes

2

If you specify a parameter name as `:class` it gets translated to `:className` before handed over to the component. So if you want to receive a parameter called `:class` you...

allow for haml like data: {tag1: "foo", tag2: "bar"} syntax

3

current you have to write `div "data-tag1" => "foo", "data-tag2" => "bar", "arial-labeledby" => "file-menu"` instead it seems natural to say `div data: {tag1: :foo, tag2: :bar}, arial_labeledby: file_menu` similar...

export_state needs new name and format

9

the export_state macro does two things: 1) creates a state variables that is shared by all instances of the component class. 2) makes the state variable publicly accessible (outside the...