feat(Tooltip): implement afterShow and afterHide callbacks

[Oupsla]

fix: #898

[gabrieljablonski]

Hey, thanks for the contribution.

Since we're already here, would you mind doing afterHide as well?

[Oupsla]

@gabrieljablonski done 😄

[gabrieljablonski]

Thanks. At first glance everything looks good. I'll test it out and review the PR later today.

[gabrieljablonski]

There's a slight issue that should probably be solved.

1. When using afterHide on a tooltip with events={['click']}, clicking anywhere outside the anchor element will trigger a handleShow(false) call, which in turn triggers the afterHide() call, which I believe is not desirable.

2. Similarly, when using afterHide on a tooltip with delayShow, hovering away from the tooltip before it is shown will trigger a call to afterHide().

There should be a check if the tooltip was actually being shown before calling afterHide(). The same for afterShow() should probably also be done, although I don't believe it will make a difference in practice.

[Oupsla]

By using useEffect, it seems to work nicely, tell me if I have understood correctly the bugs and if it is fixed.
Below some videos with my tests

events={['click']}

Screen.Recording.2023-01-12.at.08.42.39.mov

delayShow

Screen.Recording.2023-01-12.at.08.46.03.mov

[gabrieljablonski]

By using useEffect, it seems to work nicely, tell me if I have understood correctly the bugs and if it is fixed.

This fixed the problems I mentioned, but it still left the issue of the useEffect() being called on the first render.

There were a few other ways to fix this, but I ended up adding a wasShowing ref to ensure the callbacks are only called when show actually changes value.

[gabrieljablonski]

Everything should be good to go. As soon as @danielbarion reviews this, I'll merge it and do the v5.5.0 release.

[danielbarion]

The code looks good to me.

Thanks for the implementation @Oupsla!

Thanks, @gabrieljablonski, and feel free to merge when you want.