There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.
If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.
Join the Discussion. Help a fellow learner on their journey.
Ask or answer a question about this exercise by clicking reply () below!
You can also find further discussion and get answers to your questions over in Language Help.
Agree with a comment or answer? Like () to up-vote the contribution!
The last 3-4 lessons have given me errors even though i had done everything correctly, identical to the solution. They usually error on the first task and wont let me move on even though it is correct. The only way to pass the lesson is to use the ‘replace with solution’ button. This is extremely annoying, as it defeats the whole purpose of doing those tasks one at a time before moving on to the next. Instead, i have to blindly do all the tasks and then compare them to the solution, and to move on: replace my code…
I’ve run into this problem too, mostly because of spacing and/or trailing semi-colons. Instead of using ‘Replace with Solution’ button, I just make the applicable changes to the task that I’m working on. This way subsequent tasks aren’t completed in my code.
Unless I’m mistaken, the root reducer sends the action to each slice reducer. If the action type is not applicable in that reducer, it simply returns the default state for that slice.
how would a dispatch of store.dispatch({ type: 'addTodo', payload:'Understand Redux'}) know to get sent to the todosReducer? Does the action get sent to BOTH reducers, and filterReducer returns the default, and todosReducer matches the case, and then updates todos?
All of the slice reducers get called by the root reducer when an action is dispatched. Because of the default cases in the switch statements, the other slice reducers are able to handle unknown action types by just returning the existing state for that slice (i.e. so the state remains unchanged for the other slices where the action is not relevant to them).