Skip to content

Latest commit

 

History

History
23 lines (15 loc) · 1.01 KB

todo-story.md

File metadata and controls

23 lines (15 loc) · 1.01 KB
Raw

Simple ToDo

Purpose

We need to track 'ToDo' records in order to improve both timeliness and accuracy of customer follow-up activity.

Data

In this first pass at the application, we need to keep track of the following data properties:

  • id : a globally unique value for each ToDo record
  • body : the text content of the ToDo record

Actions

This edition of the application needs to support the following operations:

  • List : return a list of all active ToDo records in the system
  • Add : add a new ToDo record to the system
  • Remove : remove a completed ToDo record from the system

NOTE: In this edition, we will not track any history of completed ToDo items.

Rules

When creating a record, the client SHOULD generate and send a value for the id property. If the client does not send a value for the id, the service MUST generate one for that record. In both cases, the service MUST ensure the id value is unqiue and reject any writes that would result in duplicate id values.