Shrugsy

Try the following using a 'Custom result function': ```js export const select = createSelector(orm, session => session.Entity.all().orderBy("id", "desc")) ```

A couple others that could potentially be dropped: - `getDefaultMiddleware` export - The `callback` notation for the `middleware` property is superior in the high majority of cases given that it...

Yep definitely

Yeah, still happening on 1.7.0-beta.0 I haven't looked into it so I don't know how much trouble the fix would be, but I would say that it's a rare enough...

Additional info: This looks like it might be related to a previous experiment @phryneas tried in #841

> This PR contains the fix - but right now I've commented the fix out and am still not getting the error in CI... I'll have to drop this. @Shrugsy...

> > This PR contains the fix - but right now I've commented the fix out and am still not getting the error in CI... I'll have to drop this....

For `jest` v26.6.3, after swapping `whatwg-fetch` out for `node-fetch`, both `legacy` and `modern` fake timers work as expected. https://github.com/Shrugsy/rtk-query-jest-compatibility-test/runs/4318217563?check_suite_focus=true v27+ still needs further investigation

> Also, the toggle does cause the page layout to change and the scroll position to move. Any way to avoid that? Not a dealbreaker, just an annoyance. @timdorr @markerikson...

I understand the intent, but this arguably adds more inconsistency rather than reducing it.  The snippet titles are the same for both TS & JS tabs, so _one_ of...