How alk3mist/temno works
Project type and purpose
• This is a Python‑based CLI application (“temno”) that consumes the Yasno Outage Scheduling REST API, formats the data, and presents schedules (daily/weekly) or exports calendars (iCalendar).
• It is a single‑executable CLI tool, not a web or GUI app.
File structure
• Top‑level:
• src/temno – the CLI application package
• src/yasno_api – the standalone HTTP client + schema definitions for the external API
• doc/adr – architecture decision records
• tests/ – unit + integration tests (with VCR cassettes for HTTP replay)
• Key modules under src/temno:
• __main__.py / cli.py – Typer‑based command definitions
• bootstrap.py – dependency injection (Wireup / DI container)
• model.py, schema mapping (map_yasno.py)
• calendar.py, arange.py – core scheduling logic
• views.py – formatting output / ICS export
• Configuration: pyproject.toml (build & dependencies), .python-version, .vscode, .gitignore
README for additional insights
• Shows CLI commands: cities, streets, houses, schedule daily/weekly, ical export.
• Mentions use of uv, pipx, and warns it is a pet project sandbox.
Summary of essential architectural elements to capture
• The layered separation (Interface – DI – Domain – I/O)
• Core scheduling logic as an independent module
• Adapter modules for HTTP calls and data mapping
• Export paths: terminal vs. ICS file
• Test harness using VCR for reproducibility