Mark Erikson

Yeah, the Reselect 4.1 types require that you be very explicit and exact about the input selector types, so it can correctly infer the types of the final selector arguments....

That's the thing. I'm not actually convinced this _is_ necessary. Going back in the Redux repo, the `$CombinedState` type was added in https://github.com/reduxjs/redux/pull/3485 , to fix https://github.com/reduxjs/redux/issues/2808 . This specifically...

Taking a step back for a bit: _is_ this maybe actually "just" an issue with Reselect itself? It sounds like we've established that this started happening with the Reselect 4.1.x...

Quoting an exchange from Twitter at https://twitter.com/sangster/status/1566737486633750528 : > Essentially, we have server-hydrated data we need to load into RTKQ caches in a code-split scenario, and it's not clear how...

@phryneas I think a large part of Ben's question is, "what does that 'rehydrated state' even _contain?" I'm actually unsure myself. Looking through our code, I see logic like this:...

> I think I'm having a hard time understanding where extractRehydrationInfo fits into the Redux "lifecycle" Per Lenz's comment and the snippet I pasted above: it's primarily called in a...

Based on this discussion, I'm sort of wondering if the alpha `upsertQueryData` API we've added is maybe insufficient. We implemented it as a modification to the existing request/response logic, as...

Yeah, the only way to have the hooks use that data atm is to have a properly formatted cache entry matching the query cache key you pass into the hook....

Yeah, the queries are always run in effects, so it would be post-first-render.

I like the idea in principle, but I think we might want to take a different approach here. Having hardcoded buttons for "Noop", "RTKQ", and "!" seems a little too...