You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use redux-idle-monitor and I want to ensure that it works as expected for us in production--my idea was to do this in a front-end test by manually dispatching a NEXT_IDLE_STATE or GOTO_IDLE_STATE action. I can dispatch the actions but NEXT_IDLE_STATE starts a timer, which is not what I want, and GOTO_IDLE_STATE updates the state but never triggers my idleStatusAction.
What would you recommend?
The text was updated successfully, but these errors were encountered:
Sorry for the long delay on this, things have been stable and my work has been busy. Thanks for opening this.
I'd think you'd need some async in your tests, a delay to see if things change. A lot depends on the testing environment, the code base has some checks to detect if it's being server rendered and disables some functionality there to avoid leaks in node.js. Some of these tests might better live inside the core code itself. Definitely open to PRs if you need to modify something to make it work.
We use redux-idle-monitor and I want to ensure that it works as expected for us in production--my idea was to do this in a front-end test by manually dispatching a
NEXT_IDLE_STATE
orGOTO_IDLE_STATE
action. I can dispatch the actions butNEXT_IDLE_STATE
starts a timer, which is not what I want, andGOTO_IDLE_STATE
updates the state but never triggers myidleStatusAction
.What would you recommend?
The text was updated successfully, but these errors were encountered: