Closed besLisbeth closed 5 years ago
Thank you as always @besLisbeth!
Oh, actually, after testing it, looks like it broke the scale transition, will revert it.
Oh no, I also tested it and did not find anything. Sorry then(
No worries! I've tested it in the codesandbox and it broke the scale transition when the alert is leaving. Reverting it fixed. BUT looks like it fix only when there's more than one alert, when there's only one it's still broken. 🤔
We should investigate it.
I've just tested the v5.1.0 (before the addition of support for multiple positions) and it worked...looks like it's broken since v5.2.0. Can you take a look in the code you added in that release and see what could be causing it?
Yes, I found it. The problem with animation for the ONE leaving alert caused by condition rendering - react unmount TransitionGroup faster than it shows the exiting animation
Yeah, that make sense! Did you thought in any possible solution?
Yes! I move TransitionGroup higher on the DOM tree - to be stable and above the conditionally rendered Wrappers. But still, have problems with exiting animation - I'm trying to find the solution with 'react-select'
I can't understand what caused such strange behaviour
I'm not so worried about the react-select
thing, for all we know it can be a problem with them, I'm more worried with the broken transition thing.
Moving it higher in the tree makes it work not considering the react-select
issue?
It's strange. Now it works for the last alert in the array. But not for others.
The alerts between 1 and alerts.length are not firing onExit event
Weird stuff hahah can I see some code?
Try to pull from there and not include react-select
Code can be dirty)
that's totally fine! will take a look and see if I can help somehow, thanks!
Thank you!
Hey @besLisbeth! I took a look in the code and couldn't find a solution. So for now I will revert the changes of v5.2, so you would only be able to use multiple alerts via multiple Contexts (unless you stay in v5.2.0 - v5.3.1).
If you find a solution, we can put the feature back.
Sure, thank you. Sorry that I caused such inconvenience(
I'll try to find a solution.
No worries! If you find a solution you are more then welcome to submit a new PR!
Resolve #108