fix: useTrackRenders should be usable inside of wrappers

[phryneas]

This swaps the ParentWrapper and Wrapper components in the render function call, so that calls that require context (e.g. useTrackRenders) can also be used in user-supplied wrapper options.

Fixes #7

[pkg-pr-new]

yarn add https://pkg.pr.new/testing-library/react-render-stream-testing-library/@testing-library/[email protected]

commit: 58adfb8

[phryneas]

@jerelmiller all that said, I want to take a step back: do we really want to do this?

Especially if we add "auto-injection" of useTrackRender into play in the future, this would e.g. capture the ApolloProvider as a "rerendered component" - which might be less than desirable. Also, you might not want to track each rerender of components in Wrapper that doesn't affect the children.

This might actually kinda take a feature away, not fix one.

At this point, my gut feeling is "if you want to test it, it should be part of rendered JSX. Putting something into the wrapper is an indicator that it is important for the test to run, but not part of the test.".

[jerelmiller]

That's fair. I think I'm stuck thinking in terms of our old implementation, but your reasons for not wanting to go this route make sense.

[jerelmiller]

I trust your judgement on whether you want to actually introduce this or not but here's an approval either way 🙂

[phryneas]

I think let's close it for now. If we get a lot of feedback in this direction, we can still pick it up, or introduce something like an InnerWrapper option.