Crowdly

createSlice cannot automatically generate action creators that correspond to each case reducer function we provide

createSlice takes an object with three main options fields:

a string that will be used as the prefix for generated action types

an object where the keys are strings, and the values are "case reducer" functions that will handle specific actions

the initial state of the reducer

What possibilities does Redux Toolkit createSlice API provide for us?

All the action creators will be generated automatically based on the reducer functions we've provided

It will disable immutable copies of the state

We will be able to configure case reducers

We will be able to write shorter immutable update logic in reducers

An extra middleware will be added and automatically will throw an error whenever it sees an accidental mutation of our state.

It automatically excluded middleware to check for common mistakes like accidentally mutating the state

In the below code

what jobs did one call to configureStore provide to us?

100%

It created a Redux store using that root reducer

It automatically blocked the set up of the Redux DevTools Extension connection

It combined todosReducer and filtersReducer into the root reducer function, which will handle a root state that looks like {todos, filters}

100%

It automatically added the thunk middleware

What is the purpose of using folders in parentheses, such as (shop) or (marketing), in Next.js?

To create hidden routes that users can't access

To make routes load faster

To group related routes without changing the URL structure

To automatically generate API routes

We need to handle the "no match" case and render DefaultUI component then. Please, choose the correct prop for this.

We need to handle a route with an optional parameter: /cart/{id} - where id is optional. So that, for example, /cart/3 and /cart would be handled by the same component CartPage.

The parameter should be bound to a variable when using useParams in the CartPage component.

Please, select the correct ways to define this:

<Route path="/cart/:id" element={<CartPage />} />
<Route path="/cart/" element={<CartPage />} />

<Route path="/cart/:id?" element={<CartPage />} />

<Route path="/cart/*" component={<CartPage />} />

<Route path="/cart">
  <Route index element={<CartPage />} />
  <Route path=":id" element={<CartPage />} />
</Route>

Will this routing work? What component will be rendered by URL /users ?

Will this routing work? What component will be rendered by URL users/new ?