Instructions have developer navigate to ToDoContainer.js, which is not in any of the previous lesson instructions. The search results below are from the entire lesson wiki.

The instructions have the coder go through the code base and make updates to components based on information coming from the Airtable API. I argue that this is not a best practice. We, as developers, change api services out periodically so should write code that is loosely coupled from our data sources.

The data should be serialized (convert the shape of the data) so that it matches what the application expects. For this specific scenario, a map can convert the response into objects that the code base can already work with.

This is much better than going into the TodoListItem and changing the props for title as that component shouldn't care at all about data inbound from an API.

Instructions say to "Define a useEffect React hook with an empty dependency list". This could be a bit confusing as the dependency list is an optional array. The main technique used to run useEffect only once is to provide an empty array as the 2nd arg.

The wording, ..."with an empty list" can be in easily misinterpreted, causing the student to provide an empty array. Wording should be updated to make in unambiguous that no dependency list should be added.

Suggest changing it to something like, "Define a useEffect React hook, omitting the second argent to ensure the useEffect runs on each change."

At this point in the app, the "Add" button is still active while the timeout is counting down. A fast user is able to create and submit a todo in less than 2 seconds. When this happens, the resolver will overwrite that speedily added todo.

Recommended stretch goal: disable the add button until the persisted todos are loaded into the app. Maybe even changing its text to please wait to submit or something to that effect.