KhaosKode.Time 1.0.7

Khaos.Time

Internal time abstractions and helpers shared by the Khaos. libraries. Not intended for standalone use.*

Khaos.Time provides deterministic and system-backed clock abstractions (local, UTC, and virtual) that keep the rest of the Khaos ecosystem testable and predictable. Every packable project in this solution ships under the NuGet package ID KhaosCode.Time, and versioning is driven via MinVer + Git tags.

Features

• ISystemClock interface plus concrete implementations (LocalSystemClock, UtcSystemClock, VirtualSystemClock).
• Thread-safe virtual clock with manual advancement for deterministic testing.
• Central SystemClock.Instance for default dependency injection.
• 100% test coverage (tracked via Coverlet + ReportGenerator) with xUnit tests in tests/Khaos.Time.Tests.

Getting Started

1. Restore tools and dependencies

    cd scripts
    dotnet tool restore
   

2. Build the solution

    .\build.ps1
   

3. Run tests

    .\test.ps1
   

4. Run tests with coverage (HTML reports land in TestResults/coverage-html)

    .\test-with-coverage.ps1
   

Versioning & Releases

Semantic Versioning 2.0.0 is enforced via MinVer with the tag prefix Khaos.Time/v. All packable projects share the same version per commit. See docs/versioning-guide.md for the complete workflow, including how to:

• choose MAJOR/MINOR/PATCH bumps,
• tag a release locally,
• run the pack pipeline (dotnet pack -c Release).

Packaging

The primary NuGet artifact is produced via:

dotnet pack -c Release

Output lives under src/Khaos.Time/bin/Release (e.g., KhaosCode.Time.<version>.nupkg).

Repository Layout

• src/Khaos.Time – production library.
• tests/Khaos.Time.Tests – xUnit test suite with Coverlet instrumentation.
• scripts/ – PowerShell helpers for build, clean, test, and coverage flows.
• docs/ – product documentation, including versioning-guide.md.
• TestResults/ – generated at test time; coverage HTML lives here.

Contributing

This repo is intended for internal Khaos projects. Follow the existing coding style, keep the XML docs up to date, and ensure the scripts succeed locally before raising a PR. For breaking changes, coordinate with downstream Khaos.* maintainers since the clocks are widely shared.