rtk-query-api

Organize RTK Query API slices by creating one distinct API slice per base URL or data source. Define these slices in state-manager/api.ts and register them in reducers/rtkQueryApi.ts to ensure consistent state management.

The best way to type build.query and build.mutation endpoints is by explicitly defining both the response and argument types, such as build.query<ResponseType, ArgType>. This ensures strong type safety across your API slices.

To reshape API data or handle errors with RTK Query, use the transformResponse function to modify successful response payloads and transformErrorResponse for custom error handling before the data reaches your reducers.

Use build.query for GET requests to fetch data and build.mutation for POST, PUT, or DELETE requests that modify data. This distinction ensures proper cache invalidation and hook generation for consuming components.

Invalidate cached data in RTK Query by defining tagTypes in your API slice and attaching providesTags to queries and invalidatesTags to mutations. This ensures cached data is automatically refreshed after modifications.