[docs][rtkq] ApiProvider link on Getting Started has an unhelpful cycle

Under RTK Query’s What’s Included section, it lists the <ApiProvider /> that “Can be used as a Provider if you do not already have a Redux store.”

After following the link to find out more, the ApiProvider documentation says “Using this together with an existing Redux store will cause them to conflict with each other. If you are already using Redux, please follow the instructions as shown in the Getting Started guide.” which links right back to the Getting Started documentation we came from, which does not include any enlightening information about when to use the ApiProvider versus the Provider.

[phryneas]

It pretty much doesn’t matter. You can start with the ApiProvider now and later replace one line, or directly set up a Redux store (which is also just 5 or 6 lines).

Going from one to the other is a matter of minutes, if even that - setting up a Redux store with RTK is generally very short.

Honestly, I think you are just really really overthinking this.

[taylorkline]

I, specifically, am starting a project that I know will eventually use a Redux store, but I don’t have one yet. I could start with the ApiProvider, right? But is that the best decision since I know I will be adding a Redux store eventually, or is it better to start with the Provider?