We'll remind ourselves of what was covered yesterday so it's fresh in our minds.

When a user spends some effort creating some state (i.e., a comment on a GitHub issue), it's important to protect them from losing it by way of an accidental swipe, press of the browser's back button, or a file drop in the browser's window.

We want to be able to make comments, and first we want to ensure that we don't allow users to accidentally discard their draft comments. Additionally, we need to ensure that drafts are always associated with the appropriate record

You're no doubt familiar with persisted state, and using ember-data to help you manage it. However, when doing anything asynchronous, we have to keep context and life cycles in mind.

When a user wants to save a comment, it should be persisted to the API. Please implement this feature and meet the following requirements

• Once a save has successfully completed, the appropriate draft state should be cleared
• Your solution must behave as expected in a high-latency environment

UI State is often pertinent to the presentation layer only, is only relevant "in the moment", and can in fact be harmful if not discarded and given a clean start if a user leaves and comes back. You may be thinking that component member data is the tool for the job, but it's more nuanced than you think!

We have a little metadata area at the top of each record, and want to allow users to expand and collapse it to their heart's content! Implement this feature, and meet the following requirements:

• The expand/collapse state should not carry over from one record to another as we navigate around
• If we expand the metadata area on a record, then go somewhere else, and then come back, we should see things as we left them

Break for Lunch