Lots of reducer work to organize active Question in redux state (rather than useState). Various UX/CSS checks for Pagination state.

1 files changed, 0 insertions, 44 deletions

diff --git a/src/counterSlice.ts b/src/counterSlice.ts
deleted file mode 100644
index 1482de1..0000000
--- a/src/counterSlice.ts
+++ /dev/null
@@ -1,44 +0,0 @@
-import { createAsyncThunk, createSlice } from '@reduxjs/toolkit'
-import type { PayloadAction } from '@reduxjs/toolkit'
-
-// Define the TS type for the counter slice's state
-export interface CounterState {
-    value: number
-    status: 'idle' | 'loading' | 'failed'
-}
-
-// Define the initial value for the slice state
-const initialState: CounterState = {
-    value: 0,
-    status: 'idle'
-}
-
-// Slices contain Redux reducer logic for updating state, and
-// generate actions that can be dispatched to trigger those updates.
-export const counterSlice = createSlice({
-    name: 'counter',
-    initialState,
-    // The `reducers` field lets us define reducers and generate associated actions
-    reducers: {
-        increment: state => {
-            // Redux Toolkit allows us to write "mutating" logic in reducers. It
-            // doesn't actually mutate the state because it uses the Immer library,
-            // which detects changes to a "draft state" and produces a brand new
-            // immutable state based off those changes
-            state.value += 1
-        },
-        decrement: state => {
-            state.value -= 1
-        },
-        // Use the PayloadAction type to declare the contents of `action.payload`
-        incrementByAmount: (state, action: PayloadAction<number>) => {
-            state.value += action.payload
-        }
-    }
-})
-
-// Export the generated action creators for use in components
-export const { increment, decrement, incrementByAmount } = counterSlice.actions
-
-// Export the slice reducer for use in the store configuration
-export default counterSlice.reducer
\ No newline at end of file