Fix #3970 - Expose types allowing library consumers to build generic utils on top of @reduxjs/toolkit.

[lcharlois-neotys]

As discussed on th issue, exposing more types is a good thing as it allows library consumers to build generic piece of code on top of the library.

As I was not sure about which strategy you want to adopt, I choose to expose only the types discussed on the issue.

[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	618a363
🔍 Latest deploy log	https://app.netlify.com/sites/redux-starter-kit-docs/deploys/65bcb9f684336a0008936e22
😎 Deploy Preview	https://deploy-preview-4146--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 618a363:

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

[EskiMojo14]

My concern is that these types, because they're internal, are not particularly user friendly - they're designed to take the internal endpoint definition that you can't get a hold of easily.

I'd rather a wrapper like we have for TypedUseQueryResult/TypedUseMutationResult etc, which takes friendlier arguments and passes them to the internal types to get the final type.

[lcharlois-neotys]

My concern is that these types, because they're internal, are not particularly user friendly - they're designed to take the internal endpoint definition that you can't get a hold of easily.

I'd rather a wrapper like we have for TypedUseQueryResult/TypedUseMutationResult etc, which takes friendlier arguments and passes them to the internal types to get the final type.

It looks nice and effectively provide a more user-friendly type.
I will give a try to your porposition to see if it works in my use case.

[lcharlois-neotys]

I close this PR since the solution suggested by @EskiMojo14 in #4147 looks to better than this one.