Zack Story

sounds sensible, I am good with either of those options

I think this PR https://github.com/rt2zz/redux-action-buffer/pull/10 unwittingly broke some assumptions about how things work. I am leaning towards reverting it, but want to gather more feedback first.

I think this commit broke it: https://github.com/rt2zz/redux-action-buffer/commit/d5e7222c64a00ba177bdaf8ac1dc179244d366e8 ~~likely due to the setImmediate usage. I will revert.~~

actually @benjaminmock I am not sure what the best resolution here is. That PR solved an issue with redux-persist. Is it incorrect if the queue drains on setImmediate? I am...

note: I agree this is messy, just not sure what best resolution is. We can probably fix the original issue in redux-persist but that will take more time and care.

Yes, you can use multiple sticker components as long as they are not nested inside of each other. Regarding sticky components, I am actually not sure what would happen if...

I would expect it to still work, are you importing REHYDRATE from the right location (it changed in v5)? `import {REHYDRATE} from 'redux-persist/lib/constants'` I have not tried redux-action-buffer alongside v5...

@githubdoramon sounds like `REHYDRATE` is the wrong constant. can you show the line where you import REHYDRATE, it should be `import {REHYDRATE} from 'redux-persist/lib/constants'` and the value of the imported...

hm, I am stumped. I will try to run your code later today and see what I can find.

ok I found the issue but I do not have an easy solution. Redux Persist v5 relies on sending out an action to get everything hooked up. Since action buffer...