[Tooltip] Improve docs and warning for custom children

[brorlarsnicklas]

• I have followed (at least) the PR section of the contributing guide.

Closes #21324

[mui-pr-bot]

Details of bundle changes

Generated by 🚫 dangerJS against dae33cc

updated

[brorlarsnicklas]

@oliviertassinari @mbrookes I pushed a new commit because of the circle-ci:test_unit-1 failed. I think that it is solved in the correct way. I interpreted that the childrenProps['data-mui'] was introduced so that only the useEffect would be triggered if not in production. Was this the right way to go? Thanks in advance :)

[oliviertassinari]

Could you add a new test? (I believe the last commit break the logic, so it sounds like we need a test to help assert it behave correctly :))

[brorlarsnicklas]

@oliviertassinari Okey, I could give it a try! So you mean that we should stick to the first commit, but add a new test in the Tooltip.test.js that covers the console.error? Or did you mean that we should stick to the last commit and add a test to that?

[brorlarsnicklas]

@oliviertassinari sorry but I'm not really sure where this new test case should be placed, is it in the Tooltip.test.js?

[eps1lon]

@oliviertassinari sorry but I'm not really sure where this new test case should be placed, is it in the Tooltip.test.js?

Yes. You can take a look at the other tests using toErrorDev or toWarnDev on how you could write a test for this PR.

[eps1lon]

This is fine. But we should be careful with the name.

updated

[eps1lon]

@brorlarsnicklas Nice work, thanks!