Composing two of the same kind about react-powerplug

[gnapse]

Do you want me to work on a PR? I already implemented this exact same functionality in the library I was using internally for this: https://github.com/gnapse/render-props-compose

[renatorib]

If you want, feel free to send a PR! 😄

[renatorib]

With compose function (w/ current 1.0 behavior), when you do that

const ToggleCounter = compose(Toggle, Counter)

<ToggleCounter>
  {({ toggle, counter }) => (
    <div>...</div>
  )}
</ToggleCounter>

Is the same as doing this:

<Counter>
  {counter => (
    <Toggle>
      {toggle => (
         <div>...</div>
      )}
    </Toggle>
  )}
</Counter>

When Toggle state is changed, only Toggle component will rerendered.
But when Counter stated is changed, all inside it will be rerendered: Counter and Toggle.

Is nothing problematic or dangerous, it's just to document the behavior

[renatorib]

Yea, I like it. I already had this idea in my head for 1.0. I think it's the best way to compose without conflicts.

[gnapse]

@renatorib can you explain to me what this phrase in the README means? I'm a bit lost about it:

Because of that, when you use toggle function, only <Toggle> will be rerendered, but if you use inc or dec functions, both <Counter> and <Toggle> will be rerendered. Even using compose() utility.

It's at the end of the section of the README that talks about the composed components.

[gnapse]

Thanks, yeah, I had misread it a bit and hence I did not fully understand it.

PR submitted BTW, let me know how it's looking when you get the chance.

[renatorib]

No prob! 😄
English is not my native language. Sometimes is hard to turn my thoughts into words/sentences.

If you want to see it in action: https://stackblitz.com/edit/react-pe1ye3
Open console and click toggle button, after click counter button, and see the logs

I'll see your PR soon, thanks!