Task Manager Pro

A professional, library-based C++ Task Manager application. This project is structured as a robust starter template for modern C++ development.

Key Features

• Library-based Architecture: Core logic resides in TaskManagerLib.
• JSON Configuration: Configuration managed via config.json.
• Task Metadata: Tasks support priority and optional due dates.
• Filtering: Tasks can be filtered by priority or overdue status.
• Doxygen Documentation: Automatic API documentation generation.
• Cross-Platform: Full support for Windows (MSVC) and Linux (GCC/Clang).
• Automated Tests: CTest-based regression coverage for domain, persistence, service, CLI, and configuration behavior.

Build and Run

Prerequisites

• CMake 3.14+
• A C++17 compatible compiler
• Doxygen (Optional, for documentation)

Compilation

cmake -S . -B build
cmake --build build

Usage

./build/task_app add "Prepare release" high 2026-10-01
./build/task_app list
./build/task_app list high
./build/task_app complete 0
./build/task_app update 0 "Prepare production release" high 2026-10-05
./build/task_app update 0 "Prepare production release" high none
./build/task_app overdue 2026-10-06

Legacy task records remain readable. New records include the optional due date while preserving existing completion and priority data.

Configuration

config.json is optional. When it is missing, unreadable, malformed, or its root value is not a JSON object, the application uses these defaults:

Setting	Default
storage_path	data/tasks.txt
app_name	Task Manager

A configured value is used only when it is a non-blank JSON string. Values with the wrong JSON type or blank content fall back to the corresponding default without stopping application startup. Unknown configuration properties are ignored.

Example:

{
  "storage_path": "data/tasks.txt",
  "app_name": "Task Manager"
}

Testing

cd build
ctest --output-on-failure

The test suite covers task construction and serialization, lifecycle and persistence boundaries, priority and overdue filtering, service-level orchestration, CLI contracts, and configuration fallback behavior.

Documentation

To generate the API documentation:

cmake --build build --target docs

The output will be in docs/generated/html.

Project Structure

• include/: Header files (Library API)
• src/: Implementation files and CLI main
• tests/: Unit tests
• data/: Data storage
• docs/: Documentation and landing page

Configuration and persistence notes

Configuration controls the application name and task-storage path. Task data is persisted separately from configuration, and the repository keeps its existing file-based persistence behavior.

The configuration loader is defensive: configuration failures are treated as optional-configuration failures and do not prevent the task service from starting with safe defaults.