I noticed Date.now() is being used inside the reducer to generate a fallback action uid.
This makes the reducer function impure by depending on external state, which should not be the case when working with redux. This will cause all sorts of trouble with redux-devtools or any kind of time travelling debugger.
I'd suggesting moving the Date.now() uid fallback logic to the action generators and depend exclusively on action data inside the reducer.
For anyone having trouble with this: a simple workaround is to always pass a uid parameter when showing a notification.
I noticed Date.now() is being used inside the reducer to generate a fallback action uid.
This makes the reducer function impure by depending on external state, which should not be the case when working with redux. This will cause all sorts of trouble with redux-devtools or any kind of time travelling debugger.
I'd suggesting moving the Date.now() uid fallback logic to the action generators and depend exclusively on action data inside the reducer.
For anyone having trouble with this: a simple workaround is to always pass a uid parameter when showing a notification.