[question] Redundant wrapping (React) components in self-referencing (Rum) components about rum HOT 3 CLOSED

Do you think this is important enough to fix? Why?

from rum.

It's not that important, because there are ways to avoid creation of few-level same component hierarchies, e. g. using multi-arity functions which call the single-arity component. Moreover, after additional thinking about it I feel that complexity introduced by possible 'fix' outweighs some minor inconveniences of multi-arity components I described in the issue.

For me the biggest problem was that initially I didn't really understand nature of multi-arity Rum components (each render fn of such components produces independent instance of React component) and because of this used them incorrectly (I was adding global event handler in multi-arity component's did-mount and this handler was fired a couple of times on each event - it took some time to find the real reason of such behavior).

from rum.

I gave it a look, it can be solved by giving anonymous render fn a name, but when used, it looked really bad and confusing. Better use a standalone multi-arity render function that is called from component.

from rum.