Updating nested state without mutation
Unchanged parts (todos, the first todo) are shared between old and new state. That sharing is what makes immutable updates cheap.
Functional patterns build programs from small functions that don't change shared data: immutability keeps values safe, composition chains functions into pipelines, and currying and partial application make specialised functions from general ones.
Change the code and press Run (Ctrl+Enter). Predict what will happen first, then break it on purpose and read what changes. Your edits are saved and match the lesson page.
Ready for more? This phase has 6 hands-on exercises with automatic checks.
Practice questions
Write the code in the editor, run it, then open the model answer to compare.
Write updateTodo(todos, id, changes) that returns a new array where the todo with that id is merged with changes, without changing the original. Test it.
Write a curried filterBy(key)(value)(list) and use it to get the books by "Ruskin" from a list.
Use pipe to build total that takes a cart array of { price, qty }, multiplies each line, adds them up, and adds 18% tax rounded to 2 decimals.
Explain it without notes
What is a pure function, and why does it matter?
How do you update a nested property immutably, and why is spread called shallow?
What is the difference between currying and partial application?
Implement pipe and explain how it differs from compose.
Preview
Console
Nothing logged yet.Expected console output
Delhi Pune
true
true false true
[ 1, 20, 3 ]
Delhi Goa