Ben Durrant

`inject` modifies the existing reducer function that's being used by your store. it **also** returns that same instance of the reducer, typed to now know that that slice has been...

Adding my support for this - would be great for library authors and users. In the meantime, I've published a tiny package called [`uncheckedindexed`](https://www.npmjs.com/package/uncheckedindexed), which uses a workaround to detect...

A more detailed explanation of the change for context: Prior to Redux v5, the handling for `preloadedState` was a little hacky. There was only the one `State` type parameter for...

could either of you put together a reproduction of the issue?

fwiw if it's not possible to replicate the existing behaviour with a linked list, I'm sure we'd be open to a new memoiser instead

@psychedelicious I've opened a PR https://github.com/reduxjs/redux-toolkit/pull/4048 to allow customising the `createSelector` instance used by RTKQ. Do you reckon you could give the build a try?

I'm not convinced we can do much about this? we get the stack string by throwing and catching an Error, it's up to the platform what the stack actually looks...

if it's not in the call stack, i don't see how we'd get that information for you?

@uncaught I don't think we're going to try and parse the stack, for the reasons Mark stated. With that said, it's doable to create a stack when you first call...

@timdorr doesn't prettier already enforce LF EOL anyway? I'm open to ditching the gitattributes file but the prettierrc we use seems to already have this same opinion