Your topic report works on both sets of messages, and in the last exercise you added total and a function of your own. In this final step of the project, you’ll explain what each function takes and what it hands back, walk through one known example and its message IDs, and make a change to the report. If you’d like a refresher on how small functions pass values to each other first, look back at Combine Small Functions Into a Report.
The mentor runs this step as a short review session, a bit like showing your work to a colleague who asks good questions. Here’s how it goes:
- Explain your functions. You paste your code from the last exercise, then say what each function takes and what it returns, one function at a time.
- Walk through a known example. You trace the report for
"delivery"on this week’s messages from the call to the logged lines, naming the message IDs on the way, and say what addingtotalchanged. - Make a change you haven’t seen yet. The mentor brings a new request and an example of what an AI assistant might suggest. You decide where the change belongs, make the edit yourself, run it, and say whether the result answers the question the report is meant to answer.
Keep your passed exercise unchanged. For the extra change, use the separate mentor-practice folder in the source-code download below. Unzip it and double-click mentor-practice/index.html. Its browser editor contains a completed starting point from the last exercise. Edit the code there and press Run to see its output. This practice copy has no grading tests and needs no code editor installation.
If you prefer your own solution, paste it into the practice editor. The page handles the exercise’s export declarations for you. Use Download my code to keep a copy of your change. The mentor can help you plan, but you’ll write the change yourself.
