Capstoneintermediate6h

Go CLI Task Tracker

Design (on paper/in guided steps, since this platform can't execute Go) a command-line task tracker in Go, applying structs, methods, slices, maps, and Go's error-handling idiom.

Tracks: Go Programming

Open in Project Studio

Objectives

Design a `Task` struct and a `TaskStore` type with methods for adding, completing, and listing tasks
Use a slice or map as the underlying storage and handle a 'task not found' case with Go's (result, error) idiom
Parse basic command-line arguments to drive add/list/complete actions
Write at least one `_test.go` test file covering the core add/complete behavior

Before you start

Milestones

1. Design the Task type and storage

Define a Task struct and a TaskStore holding tasks, with methods to add and list them.

Task struct has at minimum an ID, Title, and Done field
TaskStore has an Add(title string) method returning the created Task
TaskStore has a List() method returning all tasks

2. Complete a task with proper error handling

Add a Complete(id int) error method that marks a task done, returning an error if the id doesn't exist.

Complete returns a non-nil error for an unknown id, following the (result, error) idiom
Calling code checks the error with `if err != nil` before assuming success

3. A minimal command-line interface

Read os.Args to support at least `add <title>`, `list`, and `complete <id>` commands.

Running with no recognized command prints a usage message instead of panicking
Each command calls the corresponding TaskStore method and prints a clear result

4. Write a test file

Add a _test.go file testing the core Add/Complete behavior with go test.

At least one TestXxx(t *testing.T) function exists
The test covers both a successful Complete and an unknown-id error case
Test failures use t.Errorf, not a halting assertion

References

How to Write Go Code