Assorted auto-formatting

Author: markerikson

docs/api/configureStore.mdx

@@ -150,7 +150,7 @@ const store = configureStore({ reducer: rootReducer })
 
 ### Full Example
 
-```ts
+```ts no-transpile
 // file: todos/todosReducer.ts noEmit
 import { Reducer } from '@reduxjs/toolkit'
 declare const reducer: Reducer<{}>
@@ -175,29 +175,29 @@ import visibilityReducer from './visibility/visibilityReducer'
 
 const reducer = {
   todos: todosReducer,
-  visibility: visibilityReducer
+  visibility: visibilityReducer,
 }
 
 const preloadedState = {
   todos: [
     {
       text: 'Eat food',
-      completed: true
+      completed: true,
     },
     {
       text: 'Exercise',
-      completed: false
-    }
+      completed: false,
+    },
   ],
-  visibilityFilter: 'SHOW_COMPLETED'
+  visibilityFilter: 'SHOW_COMPLETED',
 }
 
 const store = configureStore({
   reducer,
-  middleware: getDefaultMiddleware => getDefaultMiddleware().concat(logger),
+  middleware: (getDefaultMiddleware) => getDefaultMiddleware().concat(logger),
   devTools: process.env.NODE_ENV !== 'production',
   preloadedState,
-  enhancers: [reduxBatch]
+  enhancers: [reduxBatch],
 })
 
 // The store has been created with these options:

docs/api/rtk-query/created-api/endpoints.md

@@ -13,12 +13,12 @@ Each endpoint structure contains the following fields:
 
 ```ts
 type EndpointLogic = {
-  initiate: InitiateRequestThunk;
-  select: CreateCacheSelectorFactory;
-  matchPending: Matcher<PendingAction>;
-  matchFulfilled: Matcher<FulfilledAction>;
-  matchRejected: Matcher<RejectedAction>;
-};
+  initiate: InitiateRequestThunk
+  select: CreateCacheSelectorFactory
+  matchPending: Matcher<PendingAction>
+  matchFulfilled: Matcher<FulfilledAction>
+  matchRejected: Matcher<RejectedAction>
+}
 ```
 
 ## `initiate`
@@ -93,17 +93,22 @@ When dispatching an action creator, you're responsible for storing a reference t
 #### Signature
 
 ```ts
-type CreateCacheSelectorFactory = QueryResultSelectorFactory | MutationResultSelectorFactory;
+type CreateCacheSelectorFactory =
+  | QueryResultSelectorFactory
+  | MutationResultSelectorFactory
 
 type QueryResultSelectorFactory = (
   queryArg: QueryArg | SkipSelector
-) => (state: RootState) => QueryResultSelectorResult<Definition>;
+) => (state: RootState) => QueryResultSelectorResult<Definition>
 
-type MutationResultSelectorFactory<Definition extends MutationDefinition<any, any, any, any>, RootState> = (
+type MutationResultSelectorFactory<
+  Definition extends MutationDefinition<any, any, any, any>,
+  RootState
+> = (
   requestId: string | SkipSelector
-) => (state: RootState) => MutationSubState<Definition> & RequestStatusFlags;
+) => (state: RootState) => MutationSubState<Definition> & RequestStatusFlags
 
-type SkipSelector = typeof Symbol;
+type SkipSelector = typeof Symbol
 ```
 
 #### Description

docs/api/rtk-query/created-api/hooks.md

@@ -25,12 +25,12 @@ For example, if you had endpoints for `getPosts` and `updatePost`, these options
 
 ```ts title="Generated React Hook names"
 // Hooks attached to the endpoint definition
-const { data } = api.endpoints.getPosts.useQuery();
-const { data } = api.endpoints.updatePost.useMutation();
+const { data } = api.endpoints.getPosts.useQuery()
+const { data } = api.endpoints.updatePost.useMutation()
 
 // Same hooks, but given unique names and attached to the API slice object
-const { data } = api.useGetPostsQuery();
-const [updatePost] = api.useUpdatePostMutation();
+const { data } = api.useGetPostsQuery()
+const [updatePost] = api.useUpdatePostMutation()
 ```
 
 The general format is `use(Endpointname)(Query|Mutation)` - `use` is prefixed, the first letter of your endpoint name is capitalized, then `Query` or `Mutation` is appended depending on the type.
@@ -42,36 +42,36 @@ The React-specific version of `createApi` also generates a `usePrefetch` hook, a
 #### Signature
 
 ```ts
-type UseQuery = (arg: any, options?: UseQueryOptions) => UseQueryResult;
+type UseQuery = (arg: any, options?: UseQueryOptions) => UseQueryResult
 
 type UseQueryOptions = {
-  pollingInterval?: number;
-  refetchOnReconnect?: boolean;
-  refetchOnFocus?: boolean;
-  skip?: boolean;
-  refetchOnMountOrArgChange?: boolean | number;
-  selectFromResult?: QueryStateSelector;
-};
+  pollingInterval?: number
+  refetchOnReconnect?: boolean
+  refetchOnFocus?: boolean
+  skip?: boolean
+  refetchOnMountOrArgChange?: boolean | number
+  selectFromResult?: QueryStateSelector
+}
 
 type UseQueryResult<T> = {
   // Base query state
-  status: 'uninitialized' | 'pending' | 'fulfilled' | 'rejected'; // @deprecated - A string describing the query state
-  originalArgs?: unknown; // Arguments passed to the query
-  data?: T; // Returned result if present
-  error?: unknown; // Error result if present
-  requestId?: string; // A string generated by RTK Query
-  endpointName?: string; // The name of the given endpoint for the query
-  startedTimeStamp?: number; // Timestamp for when the query was initiated
-  fulfilledTimeStamp?: number; // Timestamp for when the query was completed
-
-  isUninitialized: false; // Query has not started yet.
-  isLoading: false; // Query is currently loading for the first time. No data yet.
-  isFetching: false; // Query is currently fetching, but might have data from an earlier request.
-  isSuccess: false; // Query has data from a successful load.
-  isError: false; // Query is currently in an "error" state.
-
-  refetch: () => void; // A function to force refetch the query
-};
+  status: 'uninitialized' | 'pending' | 'fulfilled' | 'rejected' // @deprecated - A string describing the query state
+  originalArgs?: unknown // Arguments passed to the query
+  data?: T // Returned result if present
+  error?: unknown // Error result if present
+  requestId?: string // A string generated by RTK Query
+  endpointName?: string // The name of the given endpoint for the query
+  startedTimeStamp?: number // Timestamp for when the query was initiated
+  fulfilledTimeStamp?: number // Timestamp for when the query was completed
+
+  isUninitialized: false // Query has not started yet.
+  isLoading: false // Query is currently loading for the first time. No data yet.
+  isFetching: false // Query is currently fetching, but might have data from an earlier request.
+  isSuccess: false // Query has data from a successful load.
+  isError: false // Query is currently in an "error" state.
+
+  refetch: () => void // A function to force refetch the query
+}
 ```
 
 - **Parameters**
@@ -128,9 +128,11 @@ type UseMutationResult<Definition> = {
 The generated `UseMutation` hook will cause a component to re-render by default after the trigger callback is fired as it affects the properties of the result. If you want to call the trigger but don't care about subscribing to the result with the hook, you can use the `selectFromResult` option to limit the properties that the hook cares about.
 
 Passing a completely empty object will prevent the hook from causing a re-render at all, e.g.
+
 ```ts
 selectFromResult: () => ({})
 ```
+
 :::
 
 - **Returns**: a tuple containing:

docs/api/rtk-query/created-api/overview.md

@@ -25,34 +25,34 @@ const api = createApi({
   endpoints: (builder) => ({
     // ...
   }),
-});
+})
 
 type Api = {
   // Redux integration
-  reducerPath: string;
-  reducer: Reducer;
-  middleware: Middleware;
+  reducerPath: string
+  reducer: Reducer
+  middleware: Middleware
 
   // Endpoint interactions
-  endpoints: Record<string, EndpointDefinition>;
+  endpoints: Record<string, EndpointDefinition>
 
   // Code splitting and generation
-  injectEndpoints: (options: InjectEndpointsOptions) => UpdatedApi;
-  enhanceEndpoints: (options: EnhanceEndpointsOptions) => UpdatedApi;
+  injectEndpoints: (options: InjectEndpointsOptions) => UpdatedApi
+  enhanceEndpoints: (options: EnhanceEndpointsOptions) => UpdatedApi
 
   // Cache management utilities
   utils: {
-    updateQueryResult: UpdateQueryResultThunk;
-    patchQueryResult: PatchQueryResultThunk;
-    prefetch: PrefetchThunk;
-  };
+    updateQueryResult: UpdateQueryResultThunk
+    patchQueryResult: PatchQueryResultThunk
+    prefetch: PrefetchThunk
+  }
 
   // Internal actions
-  internalActions: InternalActions;
+  internalActions: InternalActions
 
   // React hooks (if applicable)
-  [key in GeneratedReactHooks]: GeneratedReactHooks[key];
-};
+  [key in GeneratedReactHooks]: GeneratedReactHooks[key]
+}
 ```
 
 ## Redux Integration
@@ -102,7 +102,7 @@ The core RTK Query `createApi` method is UI-agnostic, in the same way that the R
 However, RTK Query also provides the ability to auto-generate React hooks for each of your endpoints. Since this specifically depends on React itself, RTK Query provides an alternate entry point that exposes a customized version of `createApi` that includes that functionality:
 
 ```js
-import { createApi } from '@rtk-incubator/rtk-query/react';
+import { createApi } from '@reduxjs/toolkit/query/react'
 ```
 
 If you have used the React-specific version of `createApi`, the generated `Api` slice structure will also contain a set of React hooks. These endpoint hooks are available as `api.endpoints[endpointName].useQuery` or `api.endpoints[endpointName].useMutation`, matching how you defined that endpoint.
@@ -113,12 +113,12 @@ For example, if you had endpoints for `getPosts` and `updatePost`, these options
 
 ```ts title="Generated React Hook names"
 // Hooks attached to the endpoint definition
-const { data } = api.endpoints.getPosts.useQuery();
-const { data } = api.endpoints.updatePost.useMutation();
+const { data } = api.endpoints.getPosts.useQuery()
+const { data } = api.endpoints.updatePost.useMutation()
 
 // Same hooks, but given unique names and attached to the API slice object
-const { data } = api.useGetPostsQuery();
-const [updatePost] = api.useUpdatePostMutation();
+const { data } = api.useGetPostsQuery()
+const [updatePost] = api.useUpdatePostMutation()
 ```
 
 The React-specific version of `createApi` also generates a `usePrefetch` hook, attached to the `Api` object, which can be used to initiate fetching data ahead of time.

docs/api/rtk-query/fetchBaseQuery.md

@@ -19,7 +19,7 @@ It takes all standard options from fetch's [`RequestInit`](https://developer.moz
   - Allows you to inject headers on every request. You can specify headers at the endpoint level, but you'll typically want to set common headers like `authorization` here. As a convience mechanism, the second argument allows you to use `getState` to access your redux store in the event you store information you'll need there such as an auth token.
 
   - ```ts title="prepareHeaders signature"
-    (headers: Headers, api: { getState: () => unknown }) => Headers;
+    ;(headers: Headers, api: { getState: () => unknown }) => Headers
     ```
 
 - `fetchFn` _(optional)_
@@ -60,7 +60,7 @@ export const pokemonApi = createApi({
       }),
     }),
   }),
-});
+})
 ```
 
 ### Setting default headers on requests
@@ -71,16 +71,16 @@ The most common use case for `prepareHeaders` would be to automatically include
 const baseQuery = fetchBaseQuery({
   baseUrl,
   prepareHeaders: (headers, { getState }) => {
-    const token = (getState() as RootState).auth.token;
+    const token = (getState() as RootState).auth.token
 
     // If we have a token set in state, let's assume that we should be passing it.
     if (token) {
-      headers.set('authorization', `Bearer ${token}`);
+      headers.set('authorization', `Bearer ${token}`)
     }
 
-    return headers;
+    return headers
   },
-});
+})
 ```
 
 ### Individual query options
@@ -94,14 +94,15 @@ There is more behavior that you can define on a per-request basis that extends t
 
 ```ts title="endpoint request options"
 interface FetchArgs extends RequestInit {
-  url: string;
-  params?: Record<string, any>;
-  body?: any;
-  responseHandler?: 'json' | 'text' | ((response: Response) => Promise<any>);
-  validateStatus?: (response: Response, body: any) => boolean;
+  url: string
+  params?: Record<string, any>
+  body?: any
+  responseHandler?: 'json' | 'text' | ((response: Response) => Promise<any>)
+  validateStatus?: (response: Response, body: any) => boolean
 }
 
-const defaultValidateStatus = (response: Response) => response.status >= 200 && response.status <= 299;
+const defaultValidateStatus = (response: Response) =>
+  response.status >= 200 && response.status <= 299
 ```
 
 ### Setting the body
@@ -168,7 +169,7 @@ export const customApi = createApi({
       }),
     }),
   }),
-});
+})
 ```
 
 :::note Note about responses that return an undefined body
@@ -186,9 +187,10 @@ export const customApi = createApi({
     getUsers: builder.query({
       query: () => ({
         url: `users`,
-        validateStatus: (response, result) => response.status === 200 && !result.isError, // Our tricky API always returns a 200, but sets an `isError` property when there is an error.
+        validateStatus: (response, result) =>
+          response.status === 200 && !result.isError, // Our tricky API always returns a 200, but sets an `isError` property when there is an error.
       }),
     }),
   }),
-});
+})
 ```