Don't generate the props param if it is not used

[alexnm]

Currently all React components are generated with (props) => in their signature. This should only be added if the component uses props

[vladnicula]

I'd see this as a post processing/cleaner step. When we generate the signature of the component we often don't know what plugins might need some kind of prop. We only know at the very end, when all steps did their work and no prop is used inside the component.

It's also edge casey, since the components without props are just templates now.

[alexnm]

I think this applies mostly in those template like components, which have no props. We can infer this from the UIDL by looking at the propDefinitions.

It's just a matter of a nice touch to not have it there, because I'm considering a lot of cases when people would play with a very simple component UIDL which has no props.

But I like that idea of pre/post processing tasks in our pipeline, we should give it some thought soon

This is in a way relate to #41, where I was thinking the UIDL might be validated at pre-processing, with questions like: are all the props/states declared in the interface actually used? and others of course.

[vladnicula]

Valid point with the validation of the UIDL, but it does not cover this case:

• UIDL definitions does not have props
• Plugin used automatically injects props because it uses some sort of context/global/non UIDL defined way of adding props
• The resulting code uses props even though UIDL did not specify any.

I still think we need to "trim" the code at the end, instead of assuming that NO PLUGIN EVER will add props where there are none.

[alexnm]

OK, I see your point, removing this from the milestone for now. We should discuss a bit more about the pre/post processing tasks before moving foward