Make React.forwardRef() components discoverable by TestRenderer traversal

[gaearon]

Implements #12693.

Note this doesn't make them visible to toTree(). Only to the traversal methods. It's not clear to me how they should (and whether they should at all) be represented in toTree().

[bvaughn]

This is interesting. You can find-by-type to verify that a thing is rendered in a tree (which seems useful in some cases I guess) - but the thing you find probably won't be what you expected it to be (e.g. it will be the ForwardRef component rather than a class component or a host component).

Maybe that's not a problem in practice?

[acdlite]

Makes sense to me

[gaearon]

but the thing you find probably won't be what you expected it to be (e.g. it will be the ForwardRef component rather than a class component or a host component).

I guess it depends on what you want to assert on it. You can check that it gets rendered and that it has props you expect. If you want to you can go deeper (similar to what would happen if you introduced a functional component at the top). So I think that's okay.

[sambokai]

Thank you for this! Just curious how regularly you guys usually release? :)

[gaearon]

We hope to cut a release within a week or two. We're not forgetting about it but unfortunately we were already in the middle of some substantial changes, and releasing an intermediate state was more risk than waiting it out.