Why children are now expected to be a function instead of a React component? about react-tiny-popover HOT 3 OPEN

With the release of version 5.0 came some breaking changes, hence the major version bump. React's deprecation of findDOMNode in favor of a more declarative way of tracking refs requires this change moving forward in order for the component to maintain compatibility with React's StrictMode.

Check the docs for helpful examples along with React's ref forwarding API.

Note that findDOMNode has been deprecated in StrictMode. Unfortunately, react-tiny-popover's magical way of finding the target's outermost DOM node relied on this. In lieu of it, ref forwarding is the best way to go.

Feel free to keep using version 3 for the time being, but I recommend migrating to ref forwarding, as this API is far clearer than the mysterious under-the-hood nature of findDOMNode.

from react-tiny-popover.

Thanks for clarification, but I'm still convinced that children should not be a function.
Don't you consider iterating through children and passing ref to each of them, thus delegating the responsibility of using the ref to children instead of hacking a common way of child nodes usage?

from react-tiny-popover.

I may add that functionality alongside the new functionality. Stay tuned.

from react-tiny-popover.