Support for nested reducerPaths for Redux-Toolkit-Query

I have an application with lots of apis. As every api takes up a top-level property key in the store it will eventually create lots of clutter. As a short-term solution, I’ve temporarily prefixed the reducerPath so that they are presented next to one another when inspecting the store in DevTools (e.g. apis/pokemon), but this is not ideal. For example:

{
  apis/one: ...
  apis/two: ...
  apis/three: ...
  ...
  foo: ... (application stuff)
  bar: ... (application stuff)
}

Have you thought about this problem, and maybe the possibility to keep everything under a single key? For example apis? So you’d store the definitions like this:

{
  apis: {
    one: ...
    two: ... 
    ...
  } 
  foo: ... (application stuff)
  bar: ... (application stuff)
}

[phryneas]

No. Of course you can always try to write a wrapper around it, but honestly I would not care if I were you. That repeated word will gzip just fine to probably 1 or 2 bytes, so it won’t create any significant extra bundle size.

[mtodberg]

@phryneas By following this approach for code-splitting, is it possible to prefix all endpoints for a particular set of endpoints like /users/* or /companies/*? So every endpoint url in injectEndpoints is automatically prefixed with users or companies. Otherwise this identical information has to be repeated for every endpoint definition url. https://redux-toolkit.js.org/rtk-query/usage/code-splitting