Bug?
Moderator: Moderators
Bug? #2
I have found that if you change the appState from a modelState \ onStart-list,
onLeave components in that modelState that had been activated during previous modelState changes,
are ignored on that leave.
To be more precise, I had a bool that was checked by the onRender of the appState, and I set a condition where modelState-onStart would eventually trip the bool. When that happened, it appears that the modelState never got past onRender to get to onLeave.
I fixed it by creating another modelState and had the onStart call that modelState instead, and I set the bool trip there.
I guess it makes sense, but it's an interesting flow tripper to watch out for.
I have found that if you change the appState from a modelState \ onStart-list,
onLeave components in that modelState that had been activated during previous modelState changes,
are ignored on that leave.
To be more precise, I had a bool that was checked by the onRender of the appState, and I set a condition where modelState-onStart would eventually trip the bool. When that happened, it appears that the modelState never got past onRender to get to onLeave.
I fixed it by creating another modelState and had the onStart call that modelState instead, and I set the bool trip there.
I guess it makes sense, but it's an interesting flow tripper to watch out for.