Avoid passing an identity function to createSelector

[EskiMojo14]

fixes #3930

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[netlify]

✅ Deploy Preview for redux-starter-kit-docs ready!

Name	Link
🔨 Latest commit	f3736dc
🔍 Latest deploy log	https://app.netlify.com/sites/redux-starter-kit-docs/deploys/656a0449444779000703ef28
😎 Deploy Preview	https://deploy-preview-3931--redux-starter-kit-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit f3736dc:

Sandbox	Source
Vanilla Typescript	Configuration
rsk-github-issues-example	Configuration
@examples-query-react/basic	Configuration
@examples-query-react/advanced	Configuration
@examples-action-listener/counter	Configuration
rtk-esm-cra	Configuration

[christopherschroer]

@EskiMojo14 It seems the issue is still there for some tests.

https://github.com/reduxjs/redux-toolkit/actions/runs/7062008022/job/19224920674?pr=3931

[EskiMojo14]

yeah, super odd 😕

[EskiMojo14]

found it - useQuery passes noPendingQueryStateSelector as a default selector, but it's technically an identity function except if the selected state is uninitialised

this is good enough reason to disable the check in this case, i think - ultimately an identity function for selectFromResult isn't going to be the end of the world