This program has a lot of decomposition. Which of the following functions have a decomposition relationship?

Select every one that applies, then check.

• The make_todo_list function calls the make_todo_toggle function.
  Correct. make_todo_list builds each row with make_todo_toggle(todo.completed, target_id).
• The toggle_complete function calls the lookup_todo_item function.
  Correct. toggle_complete starts with todo = lookup_todo_item(state.todos, target_id).
• The remove_todo function calls the lookup_todo_item function.
  Not quite. remove_todo builds its own new_todos list with a loop and an if todo.id != target_id check; it never calls lookup_todo_item.
• The edit_todo function calls the lookup_todo_item function.
  Correct. edit_todo starts with editing = lookup_todo_item(state.todos, target_id).
• The save_changes function calls the lookup_todo_item function.
  Correct. save_changes starts with todo = lookup_todo_item(state.todos, target_id).
• The add_todo function calls the lookup_todo_item function.
  Not quite. add_todo only builds and returns the "Create New Todo" page; there is no existing item to look up yet.

The remove_todo function uses which loop pattern that we taught you previously?

Select one answer, then check.

• The Take pattern
  Not quite. Take stops after collecting a fixed number of elements; remove_todo checks every item instead.
• The Filter pattern
  Correct. remove_todo builds new_todos by keeping every item whose id != target_id, which is exactly Filter: keep the elements that satisfy a condition.
• The Find pattern
  Not quite. Find returns one matching element (or a default); remove_todo collects every item that does not match, into a new list.
• The Delete pattern
  Not quite; "Delete" isn't one of the named loop patterns from the reference sheet. The mechanism here is Filter, rebuilding the list without the unwanted item.
• The Map pattern
  Not quite. Map transforms every element into something new; remove_todo keeps items unchanged and only decides whether to include them.

Which of the following is the best description of the target_id variable in the make_todo_list function?

Select one answer, then check.

• The target_id is an integer representing the unique ID of a todo item.
  Not quite. In make_todo_list, target_id = Argument("target_id", todo.id): it's wrapped in an Argument, not a plain integer.
• The target_id is an integer representing the index of a todo item in the list.
  Not quite, for two reasons: it holds todo.id (the item's unique ID), not its position in the list, and it's wrapped in an Argument, not a plain integer.
• The target_id is a string representing the unique ID of a todo item.
  Not quite. todo.id is an int field on TodoItem, and the value here is wrapped in an Argument, not a string.
• The target_id is an Argument object with the value of the current todo item's ID in the loop.
  Correct. target_id = Argument("target_id", todo.id) wraps the current loop iteration's todo.id, and is then passed to the row's buttons so clicking one sends that specific item's ID.
• The target_id is an Argument object with the value of the current index in the loop.
  Not quite. The loop is for todo in todos, which never produces an index at all; the wrapped value is todo.id, the item's unique ID.

The difficulty is a string in some places and an integer in others, even though it's the same conceptual thing every time (the difficulty of the todo item). Which of these statements about this is NOT true?

Select one answer, then check.

• The difficulty field in the TodoItem dataclass is an integer representing the numeric difficulty on a 1-3 scale.
  True. TodoItem.difficulty: int, filled with values like 1 from DIFFICULTY_RATINGS.
• The difficulty variable in the make_todo_list function is a string representing the difficulty as a number of stars (e.g., "⭐⭐" means a difficulty of 2).
  True. difficulty = "⭐" * todo.difficulty builds exactly that star string.
• The third argument to the SelectBox in the make_todo_list function is a string representing the difficulty as a number of stars (e.g., "⭐⭐" means a difficulty of 2).
  This is the false one, for two reasons. There is no SelectBox call inside make_todo_list at all: SelectBox only appears in edit_todo and add_todo. And even there, its third argument is a plain digit string from DIFFICULTY_RATINGS ("1", "2", "3") or str(editing.difficulty), never a string of stars.
• The new_difficulty parameter in the save_changes function is an integer representing the numeric difficulty on a 1-3 scale.
  True. save_changes(state, new_name: str, new_difficulty: int, ...) annotates it as an int, and it's stored straight into todo.difficulty.