Improve doc clarity around TypeScript and createAsyncThunk usage

[EvHaus]

I had a difficult time figuring out how to get proper TypeScript responses for dispatched thunk actions. I read the docs several times, and even though the answer was there (use type narrowing via match), I missed it each time.

I think I skipped it because the relevant information was nested under the "Manually defining thunkAPI types" category, which I wasn't doing in my case.

Since this type narrowing is very useful and relevant even when you're not manually typing thunkAPI, I'm making a proposal in this PR to move this information slightly higher in the doc and give it a dedicated section.

For more context, see my question on Discord.

I hope you'll consider making this small change. Thank you!

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[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 873a647:

Sandbox	Source
@examples-query-react/basic	Configuration
@examples-query-react/advanced	Configuration
@examples-action-listener/counter	Configuration
rtk-esm-cra	Configuration

[netlify]

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

Name	Link
🔨 Latest commit	873a647
🔍 Latest deploy log	https://app.netlify.com/sites/redux-starter-kit-docs/deploys/66a477c27d71450008bd4921
😎 Deploy Preview	https://deploy-preview-4523--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.

[markerikson]

Not sure about the "in the component" part. The preferred approach would be to use await dispatch(myAsyncThunk()).unwrap(), which would actually throw an error:

• https://redux-toolkit.js.org/api/createAsyncThunk#unwrapping-result-actions

[EvHaus]

The content, including "in the component" is a copy/paste of the existing doc. Just moved.

[EvHaus]

Pushed a new update that instead promotes the use of .unwrap() rather than modifying the previous docs.